Playwright vs. Tricentis Testim Salesforce

Easy to code and help in sanity regression and functional test cases

Incentivized

My organization heavily customizes Salesforce to align it with specific business processes, adding custom fields, workflows, and triggers. With each Salesforce release or customization update, we need to ensure that existing functionalities and customizations remain intact.Tricentis Test Automation for Salesforce excels in this scenario. Its ability to create and execute comprehensive regression test suites efficiently ensures that customizations don't introduce unexpected issues or regressions. We can automate the validation of custom workflows, triggers, and data integrity, saving time and reducing the risk of errors.

Incentivized

• API
• UI
• Performance

Incentivized

• By automating testing processes we have reduce the time and human resources required for testing and enable us for cost savings.
• Seamlessly integrates with Salesforce enviornment.
• Adapts to projects of varying sizes and complexities to scaleup.

Incentivized

• bigger adoption
• mobile testing

Incentivized

• Streamlined Test Data Management:
• Challenges: Managing test data in Salesforce, especially when dealing with complex data models and large datasets, can be challenging. While Tricentis supports data-driven testing, it can be more intuitive in terms of data generation, manipulation, and maintenance.
• Room for Improvement: Tricentis could benefit from improved test data management features, including the ability to easily create, import, and export test data. Additionally, the tool could offer more built-in data generation options, data masking capabilities, and better integration with external data sources to simplify the test data setup process.
• Scriptless Testing for Complex Scenarios:
• Challenges: While Tricentis offers a user-friendly interface for test case creation, some complex Salesforce scenarios may still require scripting knowledge. This can be a hurdle for business users or testers with limited scripting expertise.
• Room for Improvement: Tricentis could enhance its scriptless testing capabilities by providing more advanced, yet user-friendly, features for handling complex scenarios. For example, improving the visual test design interface to accommodate intricate conditional logic, dynamic data handling, and complex user interactions without requiring scripting would make the tool more accessible to a broader range of users.

Incentivized

We will renew but hope they improve their mobile experience.

Incentivized

It makes automating complex user interactions easier, fits right into our CI/CD for continuous testing, and works great across different browsers. The Documentation is a plus, you don't really need to search a lot to understand and find what you need for the coding. The community is small but very helpful, which makes it a breeze to use and a must-have for keeping our software in top shape.

Incentivized

Very good tool, first of this kind so no element to compare but still very good tool. It allows us to gain a lot of time and to be very deep in the testing phases

Incentivized

We selected Playwright over the rest for several reasons. The learning curve is faster, making it easier for our team to get up to speed quickly. The setup is pretty straithtforwared, minimal configurartion needed and a great example included in the configuration which includes all the basics to start writing using that spec as a placeholder. Compared to Cypress, Playwright support multiple browsers out of the box, giving us broader testing coverage. Appium is great for mobile testing, but extremely slow.

Incentivized

We selected Tricentis Test Automation due to it's ease of use. It was the pricier option out of the competitve pool, however, it was important for us to have a scalable solution that integrated with all of our technologies and platforms. It was the most user-friendly tool and took the least amount of time to onboard individuals.

Incentivized

• Reduce of cost of manual testers
• Reduce of released bugs
• Reduce of costs of developer time
• Increase QA Coverage

Incentivized

• Improved productivity of QA team a lot
• Efficiency of test automation scripts gone up
• Automating test cases is so easy and reduced lot of efforts