Each of us has a project: your favorite, dear, to whom you wish to grow and prosper. So, we are writing many manual tests, automating the repetitive actions, reporting hundreds of issues in Jira or any other bug management tool, and as a result, we generate a lot of data that we do not use. However, how do you assess your project's prosperity, if there are no criteria for this very prosperity?
How can you react quickly to problems before they become incorrigible, if you are not gathering any information that can give you a hint that something goes wrong?
How do you understand what should be improved, if you don't know that problems even exist in your project?
I have an answer: “Statistics!" Yes, when you hear this word in the context of testing, you might have thought that this is much better applies to sales or any other marketing field, but definitely not related to the testing process itself. That's why, instead of formulas and a list of metrics, I will tell you about my experience of collecting and analyzing statistics - and the results that I have achieved after I started using them.
Statistics is needed to effectively manage the project: diagnose problems, localize them, correct and verify whether the methods of solving the problem that you have chosen helped you. The goal is to extract the key values and present them into a compact, straightforward way.
During the presentation I will provide the following information:
- why test statistics gathering is important
- how and where to collect the statistics
- what value the test results can bring into your daily workflow
- how to make decisions based on the information you can get from the test execution statistics
- how to find a root cause of failures and solve testing-related problems
- samples of stats you can start gathering right now