I have noticed that enterprise IT companies have tons of manual test cases, creating a huge bottleneck for test execution and automation. All these companies are facing the same challenges:
- It’s hard to know what these manual tests are actually doing
- Most or all of these tests are executed manually
Change is needed! What if you could simply convert these test cases to be automatable in a few easy steps?!!
The idea is powerful: “Automate what is possible to automate.” How long do you spend to convert manual tests? Is your team motivated enough to convert all these tests? Testers should produce tests, not spend their time on tasks that can be automated. Especially facing challenges of cost restriction and time. So you will probably forget the idea of automating existing test cases and it’s sad. The good news is that all this time and energy can be saved. A new approach can now bring you a new way to do that. Let me detail the solution behind that.
When you have a manual test case, you have some documentation for manual testing, and to keep it simple I will talk about Microsoft Excel files. In your Excel sheet you will find test cases, and in each test case you will find some requirements, test step descriptions and expected results. To generate an automation script from that, you need a bit more. Test data is needed, and you usually have all this test data already in every test step! Next you can say that a test step is based on a keyword with some parameters. This is how to easily create an executable script for one test case. Now, if you step back and look at more than one test case, a pattern emerges. Of course there is a potential problem with converting test descriptions automatically. They originally created by humans and humans are not 100% rigorous about what they do. For example, the same keyword can be described using different words in a test suite. And believe me, it’s hard to manage that. But it’s now possible to extract similarities using an importer and we can help the tool to understand all these similarities. This is how to understand the manual test cases. It’s a simple explanation about how to convert some manual tests into automatic test scripts.
A second benefit is the ability to read and understand all these manual test cases; to import and create models from them. Like that you are able to modify the model based on all your test cases and also understand and see your test cases in the model explorer. All your requirements imported from the manual test cases are added in the model and you can track requirement changes! Of course from the model you can regenerate new documentation and test scripts!
To conclude, this can bring a new dimension and value to your company. It’s just the beginning of a big change where you can enter the world of model based testing. But this is much more than model based testing. This is a new way to improve control of the tests you want to generate, improve the visibility of what you are doing, and accelerate the testing speed in your company.
And you, how deal with Manual test case conversion ?
Thank you for reading! Please comment!
Read more on : https://www.conformiq.com/category/blogs/
Comments are closed