5 Questions you need to ask at every Salesforce DevOps planning meeting

December 26, 2019

By Jon Robinson, Head of North America at Provar

Test as quickly as you build.

That’s the new normal. Testing used to be thought of as an afterthought and something relegated to one of the most forgotten parts of the product phase-gate process. Now the paradigm has changed in order to help teams get new ideas to market more quickly. How? By integrating testing throughout the DevOps process. 

Within many organizations, it has become apparent that with a finite amount of resources and an increasing need to shorten the release lifecycle, testing needs to be integrated with the Continuous Integration/Continuous Development (CI/CD) tools that teams are using. 

Related to this, we’ve been consulting with a lot of customers with the aim of helping them accelerate testing and bring this approach earlier and more frequently in the development lifecycle. What we have learned is that most teams have the experience and skills to make this happen. It’s really just about starting a dialogue internally to set an organization up for success and align priorities. 

Based on these conversations, here are a few best practices that we have developed to help teams start to think about the Salesforce DevOps planning process in a proactive way. By having these important conversations early and often, you can work together to release software faster and more reliably with DevOps in mind. 

Because at the end of the day, it’s not about creating more tests, it’s about creating meaningful tests that truly protect the most important parts of your business.

 

Questions DevOps and QA teams should discuss during every Salesforce DevOps planning meeting


  1. Should we test all new functionality early and at each stage in the deployment process, or wait until it reaches a higher level environment (such as a UAT or staging environment)?
  2. Should we perform regression-based testing on all existing functionality and how often do we do this regression testing?
  3. Do we only test this feature at the end of a release cycle?
  4. How much time should we spend dealing with test data each week?
  5. How much time should it take for a single line of code to go from Development -> Production?

Every organization has its own development and testing goals and objectives. That’s why it’s important to start an internal dialogue to discuss your development objectives and talk about creating a testing strategy that can support those goals. 

 

Learn how you can test as quickly as you build with Provar. Come say hey at our booth at Cactusforce! 


We designed Provar to help teams build, test, and release software faster and more reliably with DevOps in mind. With Provar, you can bring testing earlier (and everywhere) in the DevOps lifecycle.

You can integrate Provar with industry-leading CI/CD partners like Salesforce DX, Docker, Apache Ant, Jenkins, CircleCI, Bamboo, Azure DevOps Server, GitLab, Travis CI, TeamCity, Bitbucket, Heroku, Gearset, Flosum, Copado, Blue Canvas and AutoRABIT

Stop by our booth at Cactusforce to learn how! Or, schedule a 1:1 demo with a Provar consultant at any time! See you soon!