TechValidate Research on TestRail by Gurock

Introduction

This case study of a Global 500 computer services company is based on a June 2019 survey of TestRail customers by TechValidate, a 3rd-party research service. The profiled company asked to have their name blinded to protect their confidentiality.

Challenges

The business challenges that led the profiled company to evaluate and ultimately select TestRail:

• Said the following are their top software testing pain points:
  • Identifying defects in the application
  • Having adequate time for testing
  • Keeping up with changes in techniques and technology

Use Case

The key features and functionalities of TestRail that the surveyed company uses:

• Has more than 150 Testers on their team.
• Used Microfocus ALM (HP QC/ALM) prior to using TestRail by Gurock.
• Integrated TestRail by Gurock with the following issue tracking tools:
  • JIRA
• Using the following as test automation tools:
  • Selenium

Results

The surveyed company achieved the following results with TestRail:

• Seen a 5% – 10% increase in productivity since adopting TestRail by Gurock.
• TestRail by Gurock helped solve the top challenges of:
  • Documenting test cases and plans
  • Tracking the progress of test runs
  • Tracking defects from discovery to resolution
• Realized the following benefits with TestRail:
  • Increased efficiency
  • Received transparent pricing with good value
  • Enjoyed the user and team friendly User Interface (UI)
  • Agreed it was easy to integrate with 3rd party tools
  • Improved productivity because it was easy to train users

Introduction

This case study of Ript Labs is based on a July 2017 survey of TestRail customers by TechValidate, a 3rd-party research service.

Challenges

The business challenges that led the profiled company to evaluate and ultimately select TestRail:

• Top pain points as a Tester:
  • Testing the product / project / people / process to identify risks and issues (bugs)
  • Communicating what has been identified, in the right way, to the right person, at the right time so it gets the necessary attention
  • Managing their environment for testing and development (of scripts, test code, etc.)
  • Learning about the product / project / domain to better identify and contextualize risks / issues and how best to communicate them
  • Focusing energies on the most important things and knowing when to escalate or ask for help
  • Developing strong relationships with developers, other testers, BA’s/PO’s/PM’s
  • Staying on top of trends, tools, techniques, and technologies so as to be best placed to deal with current and emerging challenges
• Top challenges that require Test Management:
  • Clearing requirements (dev team is building the wrong product)
  • Insight into development progress (tests as indicators of progression, tests as documentation, bugs and issues as indicators of risks, process challenges, etc.)
  • Deployment and the idea that progressing through various environments with associated (possibly automated) testing will increase confidence that the product can be deployed successfully and will work properly in a production situation
  • Maintenance and reproduction / documentation / communication of customer support issues, production telemetry, and testing

Use Case

The key features and functionalities of TestRail that the surveyed company uses:

• Has a single Testers on their team.
• Used the following test management tools prior to TestRail:
  • TestLink
  • Zephyr Enterprise
  • Spira Team
• Integrated the following tool with TestRail:
  • JIRA

Results

The surveyed company achieved the following results with TestRail:

• Increased their productivity by more than 20% (saved 6+ hours a week) after switching their software testing solution.
• Realized the following benefits with TestRail:
  • Increased efficiency
  • Improved flexibility due to ease of use
  • Received transparent pricing with good value
  • Enjoyed the user and team friendly User Interface (UI)
  • Agreed it was easy to integrate with 3rd party tools
  • Improved productivity because it was easy to train users