TestCase Studio: A unique tool for writing test cases and reporting bugs.

In any discussion regarding a new tool in the market, there are 4 important questions to ponder upon. WHAT, HOW, WHO and WHY? But before delving into those, let’s gauge if it brings something unique to the table or if it is similar to some of the existing products in the market. The answer is “YES” since it is different from any other existing product given the fact that it is not a record and play tool.

WHAT IS TESTCASE STUDIO?

A simple definition of TestCase Studio is a tool to generate functional test cases by converting user actions on the web application into plain English. It is basically automating the process of test case creation/documentation.

HOW TO USE IT?

There is a detailed documentation along with a 15 minutes video provided below which explains about the features along with its limitations. Also, how to install and use it. Please refer the link below:

TestCase Studio - SelectorsHub

WHO SHOULD USE IT?

This tool should not be limited to testers but also Developers, Business Analysts, Project Managers, UAT Testers and even people doing post production testing should use it.

WHY SHOULD WE USE IT?

Although, there are multiple scenarios which I can think of but I would like to highlight few which would really benefit from this tool

1. The best part is the test cases generated are accurate with absolutely 0 margin of error. Anything and everything that is being performed on the application gets translated into test steps.
2. The time that is saved from test case documentation can be invested in actual testing.
3. The XPath and cssSelectors are generated along with the test steps. Hence, while creating the automation scripts, we can refer them directly and save further time of capturing them again.
4. It saves test data along with the test steps.
5. Every single phase of testing can be documented including Ad-Hoc/Monkey/Exploratory testing. Consider a person who comes with good amount of Domain/Application knowledge. He/she would be more effective in finding bugs through exploratory testing. But this part cannot be translated to any other person since it is nowhere documented. With this tool, people can leverage documentation and can speed up in gaining the understanding of the application.
6. Last but not the least, it would be of great help for reporting and reproducing a bug.

Thank you!