ABHcardsBlogQA/Test Automation

ABH Card #4: Test automation: the problem isn’t the problem

By February 26, 2018 No Comments
The Problem is your attitude about the problem

Recently, our project was faced with a problem. We were not satisfied with the metric we use for the calculation of our test automation coverage. I was sure that the current tests we developed covered much more functionality than the numbers showed.
So, I investigated different solutions and how other teams and companies represent these numbers and figured out a new way to represent automation coverage by introducing test case weight (importance of test case in overall application) and a new parameter which indicates whether a test case is an automation candidate at all.
As a result, we now have 2 metrics: overall coverage and applicable coverage. Our coverage increased with this new calculation, since we began observing the situation logically and in a more natural way that wasn't purely mathematical. We now also have better insight on how to improve faster by giving more effort to automate test cases with greater weight.

Change your attitude, be innovative

But this approach is still flawed. I wasn't able to find an appropriate test case management tool, meaning we track cases using formulas in an Excel sheet.
That's when it hit me … I should develop a test case management tool which would be appropriate for our project first, and hopefully grow into something a wider audience could use. So, I am exercising my skills to create a new test case management tool which would introduce new functionalities and methods than we can't find on existing ones. I want it to have enough options to provide everything a tester needs but at the same time to remain simple and dynamic enough to not have to take care of certain things which are not used across different projects.

Remember, innovation takes work   

To make this possible, I have some work to do. First and foremost, I need to strengthen my knowledge and skills in certain areas. I am trying to strengthen my programming skills by attending courses after work and playing around with Ruby on Rails, HTML, CSS, Bootstrap, JavaScript and jQuery. Working on such a fast-paced project and having the freedom to jump outside of classic QA responsibilities, introduced me into the world of programming and I am trying to get better at it - both at work with the help of my development team and individually at home.