The product's areas of improvement include pricing considerations and additional features related to visual testing and PDF handling. At present, the ability to capture screenshots for specific screen elements is currently not included and requires integration with a third-party tool for the same. Also, it is complicated to work with PDF files in new windows. We have to download the file for validation purposes. They could provide these features in-built, reducing the need for users to register custom code.
There are a few minor areas where improvements are required, but they are not something that I can discuss at a high level. I will have to ask the team that uses Testim since they can give a better response to what requires improvement in the product. I only manage the team that uses Testim. I cannot be exactly described as an end user of the tool. There were some issues in the product's initial setup phase in regard to the area of documentation since it wasn't very easy to understand everything mentioned in it. There were some trial and error methods our company had to deal with while using the product's documentation, after which we were able to get through the setup phase. I want the documentation to have more information to help users with the setup process. I want the product to be more scalable in the future.
Associate Director, UX at a tech services company with 501-1,000 employees
Real User
Jun 21, 2023
I get a little bit confused while creating new branches. When I create a new branch and run the script on another branch, I am confused about whether my script is saved in the current or previous branch. Some notifications are missing from the system side.
Director Test Services at a tech services company with 201-500 employees
Real User
Aug 26, 2021
The accessibility reporting features could be more robust to be reported at the script level and allow users to map down to the step level. Some lists have values that are returned in different orders and once captured within a validation, the sort order can change. Is there a way for Testim to ignore the sort order and validate the list? Sharing steps across projects would be helpful for teams as some products are similar in features and configurations, so sharing steps upfront instead of recording them would benefit our teams.
The UI could use a better design with a better user experience in mind, for instance - instead of going in and out of the editor every time I want to view test data for a test, I could just view the test data in the table, or the ability to copy steps through tests. Reports are looking good but missing a lot of information and customization options. for example - ability to create custom reports for a specific test/suite/plan for a specific time range, or seeing additional information about failed tests in the report without entering the editor (see comment above). User actions should not be limited (e.g. not being able to delete shared steps, only being able to hide them).
There are common properties between multiple elements that we should be able to edit - such as 'when this step fails,' 'when to run this step,' and 'override timeout'. I should be able to update these properties if I select multiple elements. e.g. I added multiple validations on a single page, now i want to override the time out for all the validations. currently i have to select each element and check the 'override timeout', what is expected is I will select all the validations and change timeout for all at once.
Testim offers a comprehensive automation testing toolkit with features like smart locators and AI functionality. It supports developers and QA teams in managing testing across environments efficiently, even with UI changes.Testim is designed for automation testing with robust features such as record and playback capabilities, a smart locator system, and a reliable algorithm to maintain stability during UI modifications. Its pre-defined tests, customizable JS testing, and accessibility...
More advanced AI-based features and features on the API side would help us create better end-to-end test suites.
There is currently no room for improvement that I can identify as of now.
Testim sometimes fails due to stability issues. It doesn't always work consistently, especially after running multiple tests.
The product's areas of improvement include pricing considerations and additional features related to visual testing and PDF handling. At present, the ability to capture screenshots for specific screen elements is currently not included and requires integration with a third-party tool for the same. Also, it is complicated to work with PDF files in new windows. We have to download the file for validation purposes. They could provide these features in-built, reducing the need for users to register custom code.
There are a few minor areas where improvements are required, but they are not something that I can discuss at a high level. I will have to ask the team that uses Testim since they can give a better response to what requires improvement in the product. I only manage the team that uses Testim. I cannot be exactly described as an end user of the tool. There were some issues in the product's initial setup phase in regard to the area of documentation since it wasn't very easy to understand everything mentioned in it. There were some trial and error methods our company had to deal with while using the product's documentation, after which we were able to get through the setup phase. I want the documentation to have more information to help users with the setup process. I want the product to be more scalable in the future.
I get a little bit confused while creating new branches. When I create a new branch and run the script on another branch, I am confused about whether my script is saved in the current or previous branch. Some notifications are missing from the system side.
The accessibility reporting features could be more robust to be reported at the script level and allow users to map down to the step level. Some lists have values that are returned in different orders and once captured within a validation, the sort order can change. Is there a way for Testim to ignore the sort order and validate the list? Sharing steps across projects would be helpful for teams as some products are similar in features and configurations, so sharing steps upfront instead of recording them would benefit our teams.
The UI could use a better design with a better user experience in mind, for instance - instead of going in and out of the editor every time I want to view test data for a test, I could just view the test data in the table, or the ability to copy steps through tests. Reports are looking good but missing a lot of information and customization options. for example - ability to create custom reports for a specific test/suite/plan for a specific time range, or seeing additional information about failed tests in the report without entering the editor (see comment above). User actions should not be limited (e.g. not being able to delete shared steps, only being able to hide them).
The API testing integration is a bit lacking and can be improved. Also, if the product will allow testing of mobile apps (native) that would be great.
There are common properties between multiple elements that we should be able to edit - such as 'when this step fails,' 'when to run this step,' and 'override timeout'. I should be able to update these properties if I select multiple elements. e.g. I added multiple validations on a single page, now i want to override the time out for all the validations. currently i have to select each element and check the 'override timeout', what is expected is I will select all the validations and change timeout for all at once.