• Jessica Bennett 5
  • 0 Points
  • Member since 2020

  • Chatter
  • 0
    Best Answers
  • 0
    Likes Received
  • 0
    Likes Given
  • 0
  • 3

I am looking to expand our development offerings and looking for nearshore development teams or UK development teams to bring on board. If anyone is either from a dev team or can recommend such dev teams it would be realyl useful, i will then respond with some qualification questions. 


The area of security and confidentiality continued to position itself on top of the list when it comes to addressing the top highlighted concerns of today’s mobile users. Unlike android, Apple has taken it more seriously and have made adequate improvements and developments in terms of providing it users the best in class mobile experience while maintaining their privacy and security.

A renowned team of California iOS developers said that the growing trend of mobile shopping and purchases has further increased the need of more secure mobile environments where developers have continued to struggle for bringing more secure environments additionally in terms of several gaming and entertainment apps where in-app purchases are highly important. The team of developers further added that Apple has continued to release improved security updates and standards that have better sustained its users from all over the world.  

Hi All,

Anyone ever used "Provar" for their Salesforce Project, please let me know about the following things:-

1. How to use it ?(Is it a separate tool need to be installed like Eclipse)
2. How easy to get hands on of Provar ?

How ever after browsing over internet I found a video of it and some pros of it :-


1.It’s code-free. As I said above, investing in a lot of code to automate your testing does not make sense for a platform like Salesforce that provides so much declarative power. Your tool should have a point-and-click interface and be admin-friendly.

2.It’s flexible. Your tool should be able to tests across different environments and browsers without requiring changes to the test case. Low-quality tools commonly hardcode things that change in different environments, like Field IDs, making your tests brittle and maintenance-heavy. Avoid this.

3.It’s smart. Your tool should be able to handle minor cosmetic changes without tests breaking (e.g. moving fields on a page layout or Visualforce page). Human testers wouldn’t get confused by this, and your automation shouldn’t either.

4.It knows Salesforce. Your tool should be able to test advanced elements like Visualforce pages and the Service Cloud console. Even if you don’t use these elements yourself, it’s a good test of product maturity. Many tools struggle with embedded tables and tabs.

5.It supports integration. Your tool should be able to connect up to other systems such as databases or your email system. This will help you to do true end-to-end testing of your processes instead of looking at Salesforce in isolation.

6.It generates reports automatically. Your tool should be able to generate reports on the successes and failures of your tests. It should also have options for running tests automatically, e.g. on a nightly basis, so that you can receive a report in your emails in the morning and just scan through. (This is normally done through a continuous integration system, e.g. Bamboo.)

7.It’s Lightning ready. Even if you’re not using Lightning yet, your tool should allow you to run tests in both interfaces. This will let you make the switch later on without dependencies.

Any help is really appreciated.