Increased test coverage was a frequently cited benefit, mentioned by 4 of 9 reviewers. This suggests that Tricentis Testim enables users to test more of their applications, potentially leading to fewer defects in production. One reviewer reported test coverage reaching up to 80%.

Reduced test effort was noted by 3 of 9 reviewers. This implies that Tricentis Testim can automate testing tasks, freeing up testers to focus on other activities. One user reported a 96% reduction in test effort, while others mentioned less time spent on script refactoring and manual testing.

Increased maintenance time was a concern for 2 of 9 reviewers. This suggests that while Tricentis Testim may offer benefits in other areas, it could require more effort to maintain tests compared to other frameworks. However, one of these reviewers also reported reduced maintenance cost, indicating that the increased time may not necessarily translate to higher expenses.

Atlassian Jira is mentioned by 3 of 9 reviewers as a tool used alongside Tricentis Testim. It is used to support software development and testing workflows.

Playwright is mentioned by 2 of 9 reviewers. Playwright appears to be used in conjunction with Tricentis Testim, potentially for test automation or related development tasks.

Apache JMeter is mentioned by 2 of 9 reviewers. Like Playwright, it may be used for testing, specifically performance or load testing, alongside Tricentis products.

A significant majority of reviewers (8) use Tricentis Testim for automated testing. They utilize the tool daily to automate regression test cases and develop end-to-end and basic smoke tests. Reviewers appreciate its user-friendliness and ability to handle UI changes, as well as its capacity to automate actions in both company-controlled and third-party applications.

Four reviewers explicitly described their use cases for Tricentis Testim. These include basic smoke testing to validate page statuses, end-to-end smoke testing for functionalities like adding and editing, and regression testing for full functionality. These reviewers focus on UI testing and code-less automation, finding Testim to be a valuable tool in these areas.

Three of the 9 reviewers mentioned issues related to validating pop-up windows and tooltips. These reviewers indicated that Testim needs improvement in handling these specific UI elements, suggesting that the current functionality may not reliably capture or validate them. This can be a significant pain point in testing applications that heavily rely on pop-ups and tooltips for user interaction.

Two of the 9 reviewers cited challenges with managing multiple tabs within the browser. This suggests that Testim's current implementation may not seamlessly handle scenarios where applications open new tabs, potentially leading to test failures or requiring workarounds. Efficiently handling multiple tabs is crucial for testing modern web applications, and improvements in this area could enhance user experience.

Two of the 9 reviewers expressed concerns regarding locator stability, particularly on branches other than the master branch. This indicates that the auto-locator functionality may not consistently identify elements across different versions or environments, potentially leading to test maintenance overhead. Enhancing locator stability would reduce the need for manual adjustments and improve the overall reliability of tests.

Data-driven testing is noted as a positive feature by 2 of 9 reviewers. This suggests that the platform's capabilities in this area are well-regarded by those who utilize them, enhancing the efficiency and effectiveness of their testing processes. This functionality allows users to execute tests with varying data sets, increasing test coverage.

The record and playback feature is appreciated by some users, with 2 of 9 reviewers mentioning it favorably. This functionality simplifies test creation and automation, allowing users to quickly generate tests based on recorded user interactions. This is particularly useful for regression testing and quickly replicating test scenarios.

Four of the nine reviewers mentioned AI's role in test maintenance. Some reviewers found the AI helpful in locating and modifying scripts, particularly with locator reassignment, which they reported saved time. However, one reviewer indicated that the AI feature was not particularly useful for maintenance, only suggesting some scripts with logics.

Two of the nine reviewers discussed AI-assisted test authoring. One reviewer noted the speed of script creation compared to other tools like Selenium or Playwright due to the record and save functionality. Another reviewer reported observing AI-driven corrections during testing, though they had not directly used the AI test authoring features.

Two of the nine reviewers mentioned the self-healing components. While one reviewer noted instances where the AI appeared to correct test failures, another stated that the self-healing components had been ineffective in their experience.