Testsigma

TestSigma is easy to learn and explain to others. It is not the easiest package out there but good enough. Their support channels and documentation is superb.

The extend of what this application can do is exactly what we need as a growing team and organization. With the presence of options in TestSigma we can work and grow for many more years.

The learning curve was not to hard but TestSigma has some Layers that you need to understand in order to be proficient with it. I really recommend to watch their webinars and plan half an hour reading their onboarding documentation. After this it's just a matter of learning while playing.

I cannot have a positive thing to say about Testsigma as I have not heard from the point person managing initial stages of attempting to try out the application.

Testsigma's account representatives are very unprofessional. We started a security review, and they never completed it. When followed up regarding what was going on from their end I have yet to receive any replies via e-mail for the past month. Called their support/sales line, and the person who answered had screaming children in the background along with no professional acumen. Didn't identify that it was TestSigma just answered the phone 'Yes'. If this is how you run your company honestly, I don't have any interest in using your product, but would like to warn anyone before attempting to engage as you may well be wasting your time if your company has any scrutiny over security issues with outside vendor tools.

1)The Testsigma can be used by a new user with a minimum amount of training.
2) The test step grouping feature is another unique feature that reduces the time required to develop a new script

A substantial portion of the Testsigma team's attention needs to be devoted to the reporting feature. It has very limited capabilities at the moment.
There is a need to integrate Salesforce features.

* Low barrier to entry! I'm not an engineer and didn't want to waste time learning a programming language to get our Part 11 Validation testing framework up and running. I have been able to make hundreds of tests which are specific to user acceptance criteria yet flexible enough to handle being general build-acceptance testing.
* Instead of buying different devices or workstations with dozens of permutations, I can choose from nearly all of the currently and previously available browser/OS combinations.
* The screenshot capability as well as the video generated by each test has made writing up reports easier.

* The reporting is not at all flexible. I had to use Grafana to create a custom dashboard of the results so that my team could see at-a-glance how all the test suites which ran overnight did. In addition, I have to do a heck of a lot of massaging to get reports which an be used for the Part 11 report. I've repeatedly asked for the ability to customize the dashboard, but it's not a priority for their product team.
* Do not expect automated UI testing to be fast.
* Inability to link test suites so that when one ends, the next is kicked off. There is a workaround for this, but it requires multiple parallel user accounts.
* Plan ahead when naming your tests. The organization capacity is a little lacking, so I had to use the naming conventions to ensure I have included all the tests in the correct set in the correct order.