PractiTest Previous Solutions
NC
Nirmal Kumar Chaturvedi
Senior Software QA Engineer at a tech services company with 11-50 employees
We used HPE Quality Center. We switched because:
- Customization was too rigid.
- User-defined fields can be created, but you are limited to a predefined set of field types: user list, lookup list, string, date, and number. This covers most needs, but does have some limits. For instance, there is no checkbox option (which actually used to exist in older versions of TestDirector).
DC
Dave Carter
Test Team Lead at a computer software company with 501-1,000 employees
Prior to PractiTest we just used excel which meant we often simply recorded what we wanted to test but never documented how to test it.
View full review »When I started at this particular company, they had scatterbrained, outdated, and chaotic spreadsheets for test plans where almost 90% of the tests didn't even make sense or make it clear what the expected results were. Converting a couple of these test plans into PractiTest was amazing and made a world of difference.
View full review »Buyer's Guide
Application Lifecycle Management (ALM) Suites
March 2024
Find out what your peers are saying about PractiTest, Microsoft, Atlassian and others in Application Lifecycle Management (ALM) Suites. Updated: March 2024.
767,847 professionals have used our research since 2012.
HA
Hector Alejandro
QA Engineer at a tech vendor with 201-500 employees
I did use another solution for previous jobs. I changed because Accedo.tv, the company I work for now, is using this solution.
View full review »No, this was the first test management tool we have used.
View full review »Buyer's Guide
Application Lifecycle Management (ALM) Suites
March 2024
Find out what your peers are saying about PractiTest, Microsoft, Atlassian and others in Application Lifecycle Management (ALM) Suites. Updated: March 2024.
767,847 professionals have used our research since 2012.