Testing Conference Heisenbag: Video recordings of reports-2016 and work on the bugs in 2017
Looking at how the conferences for testers look like, we were surprised: on each of them technological issues faded into the background, and the main focus was on test management and software quality. These conferences solved the problems of PMs and CTO, and not developers and testers-automators. Is it bad? Of course not. Suum cuique, as they say.
However, doing the first Heisenbag in Moscow last year, we decided to correct the situation and make it the first purely technical conference for all those who practice testing: it’s not just testers, but also most developers (who care will be with their code). Having scored some bumps on the first attempt , we took into account the experience gained, and on June 4, we are ready to do a deep dive in testing technology for the Heisenbag 2017 Piter .
In the meantime, we share all the video recordings of the reports of the last conference and tell in detail what to expect from the next one.
')
The main point of the changes in the new conference will be the program: we received more than 250 reviews from our participants, and many of them (20 percent) complained that the program was not hardcore enough.
The most vivid example is, perhaps, Rex Black, whose reports are not even included in the top-10. With all due respect to the knowledge and experience of Rex, the reports were not very relevant and rather superficial. It was after this incident that we decided not to miss a single report without test runs and rehearsals, regardless of the status of the speakers.
And yes, despite the fact that Rex wanted to speak in St. Petersburg, this time he will not. Just like many other speakers who did not reach the rating for a passing score.
The good news is that the program is already 60% ready, and we have the time and opportunity to look for technically complex, interesting and unusual performances. We will choose with passion. In addition, at the request of participants, we screwed an indication of hardcore to each of the reports - so now you will know exactly what to expect when going to the next report.
Since three months have already passed since the last conference, we have opened access to videos of all the reports of the previous conference. There you will find everything that happened in December: reports on test automation, load testing and integration testing, and much more.
In the next post I will review the best reports of the last conference, so if there is no time to watch everything, it makes sense to subscribe to our blog (or any of the social networks) and wait for the list of the best.
In the meantime, the rating is not ready, you can evaluate how those speakers spoke, whom we have already invited to the next event with new reports. For convenience, I tried to break the reports by topic:
Alexey Vinogradov / Radio QA - Improving Autotests: a session of black magic
A report from the developer of the Selenide framework and the founder of the Radio QA podcast on how to do the right UI autotests. Which techniques should be used by a professional developer, and which ones should be avoided? Where is the pain in modern automated testing? Everything will start with a simple code and consistently go to using popular design patterns, such as: PageFactory, LoadableComponents, Single Responsibility Principle and others.
Igor Khrol / Toptal - Testing in the data world
The management of the companies tries to make decisions not on a whim, but on the basis of numbers and objective data. How to test the software that counts these numbers? If the code, after processing the company's data for the year, shows 42% - is this the correct answer, or is there an error, and we should have received 43%? Based on the practices developed by Toptal’s analytics department, I would like to answer these questions. BI, ETL, DWH, ML ... If you know what these abbreviations mean, this report is for you.
Jan Jaap Cannegieter / Squerist - Finding the best way to test your system
You can test differently, the truth is that most testers do not know about all approaches, using familiar methods even where they are not very suitable.
In this report, you will learn the difference between scripting and research testing, which testing methods are hidden under each of the approaches and in what situations they should be used, as well as how it all relates to test automation.
The second, practical part of the report will be devoted to creating a checklist that will allow you to choose the right tool or approach to your project.
Artem Eroshenko - Allure Framework
Allure Framework is a popular autotest report tool that simplifies their analysis. In the report, Artem will tell about his new version of Allure 2. A lot of new things have appeared in it: the environment, the restarts and the history of the test, the display of fixtures, the categories of errors and much more. One of the key features is the ability to customize Allure for yourself using a plugin system.
Dan Cuellar - Appium: Automation for Apps
A report from the developer Appium framework, recently included in the JS Foundation, is a cross-platform open source tool for writing UI autotests for Android and iOS. After a brief introduction to the philosophy and principles of Appium, Dan will show you how to write Appium scripts using WebDriver in your favorite language.
Here it should be noted that Dan is preparing something new: he will show the use of Appium for desktop applications. The report is still in preparation, as is the solution in the prototype stage. We crossed our fingers for Den to do it all, and he showed an exclusive report. So it will be useful to you, even if you are not a mobile tester.
Alexey Lavrenyuk / Yandex - Load testing a web-service
We are shooting at the Python Tornado demo web service, which is specially written to show performance problems. I will show how resource leakage reports, heavy cron jobs, bad algorithms and heavy database queries appear in the load test reports. We will draw conclusions, correct bottlenecks and compare the performance of the service "before" and "after."
Although many of the above reports are technologically advanced and professional-oriented, we have a whole block of reports that will be full of technical results and will require not only experience, but also love to dig deeper into the guts of your favorite technologies or your own product. So far we have two such, but there will be more (we are currently recruiting to the program for technically complex reports):
Ilya Korobitsin / Grid Dynamics - WebDriver-tests for JavaScript
For most end-to-end tests in the browser, Selenium WebDriver is used, clients to which are available in many languages. The report will reveal the experience of writing such tests in JavaScript and dealt with what features of the language had to face in the process. Protractor, a framework that simplifies the testing of applications written using AngularJS, will also be reviewed.
Andrey Satarin / Yandex - Wash your hands before eating or sanitizer in testing
As one hero said, “great responsibility comes and great responsibility”. C ++ is a language with great expressive power and enormous possibilities. But these opportunities have to be paid for with potential defects that are absent in programs in managed languages.
This report will discuss sanitizers - great tools that allow you to find complex defects in C ++ programs. Andrei will talk about these tools, their capabilities and how to use them for the benefit of your project.
And finally, the report from Ilari Henrik Aegerter , which did not fall into any of the categories, since it is dedicated to how you personally, as a tester / developer, become better, more professional and “highly paid”.
In the report you will receive a list of specific steps that can be taken immediately after the conference in order to develop in the right direction. All recommendations will be illustrated with real life cases and examples.
In addition, several reports are currently under preparation and review:
In general, we are still preparing a program, and we cannot say anything precisely about these reports - it all depends on the level of reports that speakers will demonstrate at the preliminary runs.
If you yourself want and feel the strength to talk about something hardcore and new to the Russian community of testers - give us a report ! Now we need technologically sophisticated reports with maximum immersion.
If you have already spoken somewhere and have met a warm welcome from the organizers and the audience, show us the videotape of the report - this will significantly speed up the decision making by the program committee and increase your chances of performance. Class performances in the past is one of the important criteria that traditionally guides our program committee.
Beginners should not be afraid either - we will definitely communicate with everyone. Moreover, if your topic is fresh and interesting, we will do everything to hone the content of the report, the technique of performance, timings and presentation, in general, to prepare the perfect report with you, for this we even started a special section in the blog.
As usual, program updates can be monitored on the conference website, and the list of confirmed speakers can also be monitored there.
PPS If suddenly after reading the post you wanted to register - for the first hundred tickets we have a special price that will increase with the number of tickets purchased. And for those who are far from St. Petersburg, there is an online broadcast.
However, doing the first Heisenbag in Moscow last year, we decided to correct the situation and make it the first purely technical conference for all those who practice testing: it’s not just testers, but also most developers (who care will be with their code). Having scored some bumps on the first attempt , we took into account the experience gained, and on June 4, we are ready to do a deep dive in testing technology for the Heisenbag 2017 Piter .
In the meantime, we share all the video recordings of the reports of the last conference and tell in detail what to expect from the next one.
')
Bug work
The main point of the changes in the new conference will be the program: we received more than 250 reviews from our participants, and many of them (20 percent) complained that the program was not hardcore enough.
The most vivid example is, perhaps, Rex Black, whose reports are not even included in the top-10. With all due respect to the knowledge and experience of Rex, the reports were not very relevant and rather superficial. It was after this incident that we decided not to miss a single report without test runs and rehearsals, regardless of the status of the speakers.
And yes, despite the fact that Rex wanted to speak in St. Petersburg, this time he will not. Just like many other speakers who did not reach the rating for a passing score.
The good news is that the program is already 60% ready, and we have the time and opportunity to look for technically complex, interesting and unusual performances. We will choose with passion. In addition, at the request of participants, we screwed an indication of hardcore to each of the reports - so now you will know exactly what to expect when going to the next report.
Video recordings Heisenbag 2016 Moscow
Since three months have already passed since the last conference, we have opened access to videos of all the reports of the previous conference. There you will find everything that happened in December: reports on test automation, load testing and integration testing, and much more.
In the next post I will review the best reports of the last conference, so if there is no time to watch everything, it makes sense to subscribe to our blog (or any of the social networks) and wait for the list of the best.
Heisenbag 2017 Piter Reports
In the meantime, the rating is not ready, you can evaluate how those speakers spoke, whom we have already invited to the next event with new reports. For convenience, I tried to break the reports by topic:
Approaches and Patterns
Alexey Vinogradov / Radio QA - Improving Autotests: a session of black magicA report from the developer of the Selenide framework and the founder of the Radio QA podcast on how to do the right UI autotests. Which techniques should be used by a professional developer, and which ones should be avoided? Where is the pain in modern automated testing? Everything will start with a simple code and consistently go to using popular design patterns, such as: PageFactory, LoadableComponents, Single Responsibility Principle and others.
Igor Khrol / Toptal - Testing in the data worldThe management of the companies tries to make decisions not on a whim, but on the basis of numbers and objective data. How to test the software that counts these numbers? If the code, after processing the company's data for the year, shows 42% - is this the correct answer, or is there an error, and we should have received 43%? Based on the practices developed by Toptal’s analytics department, I would like to answer these questions. BI, ETL, DWH, ML ... If you know what these abbreviations mean, this report is for you.
Jan Jaap Cannegieter / Squerist - Finding the best way to test your systemYou can test differently, the truth is that most testers do not know about all approaches, using familiar methods even where they are not very suitable.
In this report, you will learn the difference between scripting and research testing, which testing methods are hidden under each of the approaches and in what situations they should be used, as well as how it all relates to test automation.
The second, practical part of the report will be devoted to creating a checklist that will allow you to choose the right tool or approach to your project.
Frameworks and tools
Artem Eroshenko - Allure FrameworkAllure Framework is a popular autotest report tool that simplifies their analysis. In the report, Artem will tell about his new version of Allure 2. A lot of new things have appeared in it: the environment, the restarts and the history of the test, the display of fixtures, the categories of errors and much more. One of the key features is the ability to customize Allure for yourself using a plugin system.
Dan Cuellar - Appium: Automation for AppsA report from the developer Appium framework, recently included in the JS Foundation, is a cross-platform open source tool for writing UI autotests for Android and iOS. After a brief introduction to the philosophy and principles of Appium, Dan will show you how to write Appium scripts using WebDriver in your favorite language.
Here it should be noted that Dan is preparing something new: he will show the use of Appium for desktop applications. The report is still in preparation, as is the solution in the prototype stage. We crossed our fingers for Den to do it all, and he showed an exclusive report. So it will be useful to you, even if you are not a mobile tester.
Alexey Lavrenyuk / Yandex - Load testing a web-serviceWe are shooting at the Python Tornado demo web service, which is specially written to show performance problems. I will show how resource leakage reports, heavy cron jobs, bad algorithms and heavy database queries appear in the load test reports. We will draw conclusions, correct bottlenecks and compare the performance of the service "before" and "after."
Testing deep dive
Although many of the above reports are technologically advanced and professional-oriented, we have a whole block of reports that will be full of technical results and will require not only experience, but also love to dig deeper into the guts of your favorite technologies or your own product. So far we have two such, but there will be more (we are currently recruiting to the program for technically complex reports):
Ilya Korobitsin / Grid Dynamics - WebDriver-tests for JavaScriptFor most end-to-end tests in the browser, Selenium WebDriver is used, clients to which are available in many languages. The report will reveal the experience of writing such tests in JavaScript and dealt with what features of the language had to face in the process. Protractor, a framework that simplifies the testing of applications written using AngularJS, will also be reviewed.
Andrey Satarin / Yandex - Wash your hands before eating or sanitizer in testingAs one hero said, “great responsibility comes and great responsibility”. C ++ is a language with great expressive power and enormous possibilities. But these opportunities have to be paid for with potential defects that are absent in programs in managed languages.
This report will discuss sanitizers - great tools that allow you to find complex defects in C ++ programs. Andrei will talk about these tools, their capabilities and how to use them for the benefit of your project.
And finally, the report from Ilari Henrik Aegerter , which did not fall into any of the categories, since it is dedicated to how you personally, as a tester / developer, become better, more professional and “highly paid”.In the report you will receive a list of specific steps that can be taken immediately after the conference in order to develop in the right direction. All recommendations will be illustrated with real life cases and examples.
In addition, several reports are currently under preparation and review:
- A report on JUnit5, which is one of the hottest topics of recent months.
- Showcase from the guys from HERE, who are going to share their work in DevOps & CI processes.
- A very juicy report from the guys from Badoo, who will share their experience in taming thousands of Gherkin tests.
In general, we are still preparing a program, and we cannot say anything precisely about these reports - it all depends on the level of reports that speakers will demonstrate at the preliminary runs.
Call for papers
If you yourself want and feel the strength to talk about something hardcore and new to the Russian community of testers - give us a report ! Now we need technologically sophisticated reports with maximum immersion.
If you have already spoken somewhere and have met a warm welcome from the organizers and the audience, show us the videotape of the report - this will significantly speed up the decision making by the program committee and increase your chances of performance. Class performances in the past is one of the important criteria that traditionally guides our program committee.
Beginners should not be afraid either - we will definitely communicate with everyone. Moreover, if your topic is fresh and interesting, we will do everything to hone the content of the report, the technique of performance, timings and presentation, in general, to prepare the perfect report with you, for this we even started a special section in the blog.
As usual, program updates can be monitored on the conference website, and the list of confirmed speakers can also be monitored there.
PPS If suddenly after reading the post you wanted to register - for the first hundred tickets we have a special price that will increase with the number of tickets purchased. And for those who are far from St. Petersburg, there is an online broadcast.
Source: https://habr.com/ru/post/323628/
All Articles