ACCELQ test automation tool
December 06, 2022
ACCELQ test automation tool
Score 7 out of 10
Vetted Review
Verified User
Modules Used
- Automate Web
- Automate Manual
- ACCELQ API
Overall Satisfaction with ACCELQ
Our organization has been going through a digital transformation, and as part of that, we were looking for an automation tool that can work across multiple platforms such as mainframe, web, API, etc.; our existing solutions, including open-source selenium, were not working in this situation and hence we were looking for one solution that can address most of the automation needs. Piloted four solutions, including ACCELQ, and conducted POCs, including migration of existing scripts. Based on the POC results and user experience, we picked ACCELQ as the solution to move forward with.
- Scriptless and hence coding is easy.
- Maintenance of the scripts are easy.
- Learning curve is small.
- The tool is not developer friendly and hence adoption across developers is low.
- The tool does not have an admin console to manage the users centrally.
- Different types of licensing and it’s all user based and hence pricey.
- Suitable for multiple platforms.
- Easy adoption.
- Less support effort.
- Overall adoption of an automation tool went up.
- Migration of existing selenium scripts to ACCELQ was relatively easy and less effort.
- Lack of overall admin console and hence managing the agents across different execution is difficult.
- Integration between accelQ and any test management tool can be difficult and buggy in most cases, even though it can be coded.
When we implemented ACCELQ, we conducted POCs with many similar solutions. Among the tools we pursued at that time, accelQ stood out against Tricentis Tosca and QMetry automation studio. However, subject 7 did better. However, they were still in the nascent stages of building the tool, and hence we did not pick it.
Do you think ACCELQ delivers good value for the price?
Yes
Are you happy with ACCELQ's feature set?
Yes
Did ACCELQ live up to sales and marketing promises?
No
Did implementation of ACCELQ go as expected?
Yes
Would you buy ACCELQ again?
No