Jevgeni Demidov Pipedrive

BIO: Jevgeni has been in the software development industry for seven years now. During his journey in this field, he managed to participate in a lot of different software testing activities, from organizing a software testing process from scratch and ending with a development of utilities that help to improve the product’s quality.

He started as a Quality Assurance Engineer back in 2011, where he was working on mobile devices and software solutions for police, courts, and other governmental structures. Later gradually and for a long time, he moved into the position of Quality Assurance Manager where he began to develop in the field of management. Currently, with somewhat understanding of the meaning of both “Test” and “Management” words, he decided to continue his career as a Software Development Engineer In Test. In this position, he has an opportunity to get more experience in all parts of product creation, including software development itself and applying his test expertise in both software related development and testing activities.

To all of the above, during his journey in Quality Assurance area, he always loved analyzing the non-standard situations, identifying what caused the problems and applying new approaches to solve them.

Presentation: How-To Guide: Statistics Based on the Test Data
session level: beginner

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.

Take-aways:

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