Summary
Key results
Shortened regression time across subsequent sprints through the introduction of test automation using Tricentis Tosca
Improved stability of Salesforce releases and shorter time to implement changes
Greater efficiency of testing in a global IT environment
Salesforce became a key platform supporting sales and customer service on a global scale. With the execution of the digital transformation strategy, the number of implementations, integrations, and functional changes increased. Manual testing could not keep up with the pace of development – regression cycles were taking increasingly more time, and QA teams were burdened with repetitive tasks.
The client needed a solution that would:
- Accelerate the verification of changes in Salesforce
- Organize test cases and data
- Ensure consistency of the testing process across multiple sprints
- Reduce operational costs without compromising quality
Comprehensive test automation in Tosca
Sii Poland provided a team of QA experts who implemented a full regression test automation process for Salesforce in the Tosca environment, in line with Tricentis best practices. The project started with an Architect and 2 Tosca automation experts, and as the scope of work expanded, the team grew to 6–8 people.
The scope of work included:
- Verification and standardization of test cases – creation of new “ready” and “done” definitions, and unification of test data
- Implementation of the automation architecture – configuration of Tosca Test Automation, repository, test structure, and Risk-Based Assessment process
- Regression automation – preparation and execution of test scenarios for subsequent sprints
- Reporting optimization – implementation of standardized reports for stakeholders and documentation of the entire automation process
- Integration with Jira – linking test automation with task management and QA workflow
The new testing model ensured full transparency of QA activities and enabled more efficient sprint planning. Development teams gained immediate feedback on the quality of changes introduced in Salesforce.
Faster releases, higher quality, lower costs
Regression test automation streamlined the way changes in Salesforce are verified and relieved QA teams from repetitive manual testing. Thanks to consistent Definition of Ready and Definition of Done criteria, each new functionality enters testing in a clear and controlled state, reducing rework and last-minute fixes.
Shortened regression cycles across subsequent sprints enabled teams to close iterations faster and plan releases with greater confidence. Instead of treating testing as a source of delays, the organization gained a predictable QA process that keeps pace with Salesforce development. More stable releases reduced the number of post-deployment fixes and minimized downtime for business users.
From a cost perspective, the reduction of manual testing and elimination of redundant test cases translated into tangible operational savings. Today, IT teams can handle a higher volume of changes without proportionally increasing QA resources, and automation has become a permanent element of the development model – not a one-time improvement. The starting point was a fully manual Salesforce testing model, and over the course of the engagement, the organization achieved nearly 100% test automation coverage.