Briefly about the event
Conference: Heisenbug 2017 Moscow
Date: December 8-9, 2017
Free webcast (first hall only): webpage on the official site .

What is the most common question in the comments on Habré? “Will there be a record?” Immediately we take the bull by the horns: the record will be, as always, in 3-4 months. But of those who asked the question, it will be barely half to watch it.

To understand why this is happening, you need to figure out - how do we watch the video from conferences, why is it even necessary?

Video is not only a show and a reason to discuss something together. You can also consider it as one of the best types of documentation.

As developers, we do not often think that there are several ways to write documentation. At the dawn of the appearance of the Runet, Vlad Balin wrote about this well .

Documentation is of different types, at least:

• “Treaty” - when several people must equally understand something important;
• "Reference" - reference information, which is verified a lot and often. It includes all sorts of international standards, dictionaries, and even POSIX type API descriptions; this also includes JavaDoc and comments in the code;
• “Learning material” - reporting new knowledge in a structured and understandable way;

The report from the conference combines several roles at once. Initially this is a kind of live performance, concentrated, useful information for learning.

But if the report on Selenium is read by the creator of Selenium and states that in the future the project will develop in a certain way - this is a kind of agreement fixed on the video. You can show this to your friends and say, “Ha, look, we have a promise from Simon Stewart himself that this will work like this.” The lucky ones, who came to the conference live, can also promise this promise in a special discussion area.

If the speaker fully and comprehensively describes some part of the system, then in the future it can be used as a reference book. You will be able to access this video over and over again, think over, revise, use the data from it when writing code or when compiling your own documentation.

Obviously, the report and its video have a certain life cycle . The report has the maximum value at the start, when a person can quickly and easily absorb all this information and immediately put it into practice. After the conference is over, it gradually turns from a textbook into a reference book. While the video is in the closed access - this is a directory with special know-how, available only to conference visitors. After opening in 3-4 months and posting on YouTube, it becomes public information, to which you can throw the link to friends, indicating the exact time of viewing. Six months or a year after graduation, it starts to become obsolete, but the next conference picks up the baton. Obsolescence is more about frameworks and specific technologies, but fundamental reports on computer science, building the development process and testing, and so on - they can continue to be used for several years for sure. It turns out such a global circulation of reports in nature.

The main problem of delivering information in the form of lectures and writing textbooks is that there are usually no people in an organization who can hold such a lecture . Or they are, but busy with something else. Or they are simply not as good as conference lecturers - few people can tell about Selenium better than Simon Stewart - the living embodiment of Selenium on earth.

That is why we don’t want to watch conference videos after 4 months, but to participate in this conference live. This is a completely logical desire and way to use the proposed material to its fullest.

Unfortunately, not everyone can fly through half the world live. Not all let go of employers. In the end, someone might not have enough budget.

Sometimes it is much more useful to gather in front of a large plasma in the office and discuss the report with colleagues in full voice, not being afraid to interfere with someone, using the full power of the Russian language and Russian mat.

And sometimes, you just want to sit at home in front of the big screen, without having to join a huge crowd of people and go somewhere. Sleep well at home, not in a hotel - after all, the conference lasts a full two days.

All these problems solves the online broadcast. You can watch anything and anything. Despite the fact that the conference brings the greatest benefit if you come there alive and participate in discussion zones, the online broadcast also has a lot of unique advantages.

How to connect to the broadcast

Previously, we posted on Habr links to various playlists on YouTube and warned: “This link is for the first day, this one is for the second, this one is for something else.” You needed to save the link to this habrapost and then follow its updates.

There is a way much easier. Free broadcast can be viewed directly from our site, here on this link:

https://heisenbug-moscow.ru/online-free/

This link is the ultimate source of truth. It is there that displays the latest, current program. There is also a big orange link “Chat with participants and ask a question to the speaker” , which leads to Telegram, participants can use it not only for paid, but also for open broadcast.

Changelog

The development of the conference is very similar to the development of a software platform. Our languages ​​and platforms are constantly competing with each other: for example, Java is chasing .NET by the syntax of the main language, and .NET is trying to catch up with Java by cross-platform. As soon as a new idea appears, implementations of this idea begin to appear in all popular technologies.

Creating conferences is very similar to the development of a software platform. JUG.ru Group has its own platform, a list of basic features. As soon as one of the conferences improves something, everyone else receives an update. This year, including this fall, there have been many conferences, and many things have improved.

Live streaming is exactly what we all want and expect to see from a good conference. To improve the broadcast, it is often enough just to add more high-quality equipment and properly configure it. Therefore, broadcast received for this autumn the maximum number of useful updates.

• Improved sound quality. Microphones stand correctly and work better, the acoustics of the hall are thought out, minor technical problems are solved;
• Video at 1440p - the extra space is used to simultaneously display the speaker and FullHD slides (or the laptop screen for live coding) on ​​one screen. Very useful tech feature;
• Infrastructure for working with video moved to the cloud, which lowered the probability of equipment failures. This is done in SBTG.ru , which help in recording the conference, and we are only reaping the fruits of their work;
• Our service infrastructure also moved to Amazon. It used to be just Hetzner, but quality uninterrupted transmission is more important;
• In the intervals between presentations, when speakers and participants on the site are retired to the discussion zones, we show the online broadcast to the audience reports and interviews with speakers and sponsors. This time the interview should be livelier; two presenters will lead them ( @phillennium and @olegchir - you can regularly see our posts on Habré);
• Many minor technical problems were solved, which most did not even notice, but they were there. In general, the feeling of watching the broadcast should be better.

Restrictions

• In the open broadcast, only the first hall is available, including keyouts. You cannot watch what happens in other halls. And there will be many interesting things. Next time register and watch everything without restrictions.
• There will be no video recordings. That is, they, of course, will, but only for conference participants who have left feedback. And for all the others, we traditionally post them in 3-4 months.
• An open broadcast is provided on the principle of as is : we are sure that everything will be fine, but if suddenly that - do not judge me! The participants of the paid closed broadcast receive special support - they are buying exactly the service.

Program

The conference is held for two days. The first day starts at 10.00, the second - at 10.30. Each day ends with a final keyout (at 17.35 and 18.15 respectively). The current program of the first hall can be seen on the broadcast page .

The first day. December 8th.

Pandora's White Box

Nikita Makarov / Classmates

In the testing industry, a lot is said about the “black box”, but occasionally “white” is mentioned. This is due, among other things, to the fact that testing the “white box” has always been considered the prerogative of programmers.

• How to prevent programmers from writing the wrong code?
• How to embed crashes in the code so that it does not hurt painfully?
• Why would you need source code parsing and what can you get from it?
• Social code analysis and coverage - why and why?

In this report we will see the answers to these and other questions, with examples and a clear demonstration.

Nikita Makarov

He worked in outsourcing and grocery companies. He was engaged in the automation of embedded operating systems based on Linux, integrated VPN solutions for business, software and hardware systems. Since January 2012, he has been the head of the test automation group in the Odnoklassniki project.

Tester Tools

Julia Atlygina / ALM Works

The purpose of the report: to show the tools that can be used on the same day, which will speed up the work of manual testers, as well as analysts, developers and others. Many people think that manual tests can be accelerated only by automation - but this is not quite true :)

In this report, I would like to show simple tools that would allow you to spend less time and at the same time help to increase the test coverage. Target audience: manual testers, as well as all those who at least sometimes need to analyze and do something with their hands.

Julia Atlygina

In testing over 9 years, the last of which spent in ALM Works, developing plugins for Atlassian JIRA and Confluence. The role of the tester combines with the roles of the Product Owner and SAFe consultant. If you have questions about JIRA, feel free to ask!

Testing the performance of web applications on the browser side (javascript, rendering, that's all)

Vladimir Sitnikov / Netcracker

Often, the word "performance testing" means only testing the server side. Much less often test directly the browser. In the simple case, we connect Yandex.Metrica and / or Google Analytics, and go ahead. But there is a nuance: in the corporate environment, sending data to NM / GA may not be available, and simply connecting NM / GA is not enough to collect the necessary amount of information about the application's performance.

In the report we will look at how to measure the duration of operations in the browser. Find out why the times obtained from Selenium show the weather, find out what the benefits of Selenium tests can be when measuring performance. Let's look at boomerang.js and find out what moments to pay attention to when integrating such libraries into a project. The report does not address the issues of optimizing the browser / server.

Vladimir Sitnikov

For ten years, it has been working on the performance and scalability of NetCracker OS - the software used by telecom operators to automate network management processes and network equipment. He is interested in Java and Oracle Database performance issues. His responsibilities include planning load measurements, analysis and explanation of the results. Vladimir is a committer in Apache JMeter.

How to check the system without starting it

Andrey Satarin / Yandex

The systems we develop become more complex every day. And it seems that there is no salvation from the omnipresent complexity that penetrates everything. One aspect of this complexity is configuration. On the one hand, the configuration greatly affects the stability and availability of the system, on the other - very little attention is paid to checking its correctness.

The report will tell you how we test the configuration and how it was useful in our project. This report will be useful to anyone who wants to learn a simple way to increase the stability and availability of the system in production.

Andrey Satarin

Engaged in testing distributed systems in Yandex. In his career, he managed to work in completely different projects: he tested the game at Mail.ru, the cloud detection system at Kaspersky Lab, the system for calculating currency prices at Deutsche Bank. Interested in testing backend and distributed systems.

The (Ab) use automation test

Alan Page / Unity

If you are a tester writing code, then most likely your work includes test automation — in particular, writing tests that automate the user's workflow. Being a veteran of automated testing (for twenty years now, and this figure continues to grow!), Alan Paige has seen a lot of teams whose attempts to do automation at least once and for all turned out to be completely unsuccessful. Nevertheless, he managed to take part in the few teams that did it all, and on this report he will share his wisdom and the patterns that really work (and also share a bunch of patterns that are worthless).

Alan will show successful automation strategies, how to deal with flaky tests, guide the dangers of UI automation and give a number of other tips, based on many years of experience in test automation in a variety of large products. You can be an advanced tester, or on the contrary, just start a career - in this report you will find tips for everyone, and such tips that can be put into practice almost instantly.

Alan Page

Alan Page has been working as a software tester for about 25 years. He was the main author of How We Test Software at Microsoft, and was involved in the creation of "Beautiful Testing Software Test Automation" . In addition, he writes articles on various engineering topics in his blog, his posts can be found everywhere on the Internet. His latest "book" is a collection of essays on automatic testing under the common name "The A Word". Alan joined Microsoft and became part of the Windows 95 team, and has since worked on multiple releases of Windows, on earlier versions of Internet Explorer and Office Lync. Including, Alan worked for two years at Microsoft as director of testing. In January 2017, Alan left Microsoft for the position of director of quality at Unity.

Testers' home classification from a developer’s point of view

Nikolai Alimenkov / XP Injection

Testers often talk about confrontation and conflicts with developers. But there are teams where everyone lives in peace and harmony. Apparently, something is wrong here? I would like to talk about how testers see the developers themselves. The report will be a fun classification. In addition to the famous monkey tester, the fly tester, the Nazi tester, the panda tester and many other heroes will be presented.

You can once again think about how you are seen from the side and, perhaps, make a difference for the better. The report will also be useful to project managers and team leaders. You will be able to quickly recognize those or other patterns of behavior testers and take measures to improve the level of teamwork. Come, it will be interesting!

Nikolay Alimenkov

Practicing java techlide and Delivery Manager. An expert in Java development, Agile practice and project management. Develops in Java for more than 12 years, specializes in the development of complex distributed scalable systems. Active participant and speaker at many international conferences. Founder and trainer of the XP Injection training center. The organizer and ideologist of the conferences is Selenium Camp, JEEConf, XP Days Ukraine and IT Brunch. Founder of the Anonymous Developer Club.

Second day. 9th December.

Simplicity, trust, control - three pillars of web testing automation

Artem Eroshenko / Independent Consultant

Report on the automation of web interfaces from the author of the tools Allure and HtmlElements.

Long engaged in projects related to the automation of web testing, Artem formed a set of rules that ensure comfortable work for him and his team throughout the life of the entire project, from the first test to several thousand. This set of rules is conventionally divided into three groups: "Ease of development", "Trust in results" and "Quality control".

The report will discuss tools that allow Artem with the team to create and edit tests as simply and clearly as possible. There will also be considered approaches that help to achieve confidence in the results of passing tests for the whole team. And Artem will talk about how to monitor the quality of tests in their projects.

Artem Eroshenko

More than 8 years of experience in automating web application testing. During this time, he worked in different teams and in different roles: testing automator, testing tool development team manager, testing automation team leader. Artyom has extensive experience with popular tools (Selenium, HtmlElements, Allure, Jenkins). Programs mainly in Java, Groovy.

Developer + Tester = Quality ++

Nikolai Alimenkov / XP Injection

In Agile approaches, the attitude towards the quality and role of the tester changed. Now the whole team is responsible for testing and product quality. But few people imagine how these approaches work in practice, how testers interact with developers, what stages a task goes through on the way from requirements to reception by the customer, who does what at different stages.

There are not so many teams where practicing the close work of a developer with a tester. In some projects this approach is avoided for the sake of saving the developer’s time, on others for the sake of preserving the independence of the tester’s opinion. Developers also do not always understand what the tester can actually help them with in practice. However, this bundle can significantly improve the quality of the product and avoid many problems.

In the report we will talk about the motivation of the developer’s pair work with the tester, specific practices and approaches at different stages of working on tasks, as well as the benefits that both parties can derive from such work.

Nikolay Alimenkov

Practicing java techlide and Delivery Manager. An expert in Java development, Agile practice and project management. Develops in Java for more than 12 years, specializes in the development of complex distributed scalable systems. Active participant and speaker at many international conferences. Founder and trainer of the XP Injection training center. The organizer and ideologist of the conferences is Selenium Camp, JEEConf, XP Days Ukraine and IT Brunch. Founder of the Anonymous Developer Club.

We build our own test framework, with Jenkins Pipeline and libraries

Oleg Nenashev / CloudBees

The appearance of Pipeline has changed the approach to automating tasks in Jenkins, especially in the case of parallel builds and tests. It is possible to build your own test framework in it and provide it to automatists as a set of libraries.

Using the example of Java projects, we will show how you can build Pipeline libraries for QA tasks and transfer projects to a new platform. We integrate Docker, Maven, JUnit, FindBugs, overity, and then we implement dynamic parallelization of tests. We will also talk about pitfalls and how you can effectively develop, test and maintain such frameworks.

Oleg Nenashev

The developer at CloudBees, is a core team of the Jenkins project. Since 2008 he has been engaged in automation, infrastructure and framework building for large software and hardware projects with the help of Jenkins and dozens of other tools. Writes code, supports Jenkins core and plugins, organizes meetings in St. Petersburg and other cities.

Development and Testing with Google

Vsevolod Brekelov / Grid Dynamics

A report for testers and developers who are interested to know: what rakes can arise when working with Google Cloud Standard Environment, how to avoid them (test), what Google tools you can take and use in your projects. You will also learn a little more about GAE, Memcache, Task Queues, Objectify, Protobuf, Bazel.

Vsevolod Brekelov

Over 5 years in software testing / test automation. The last year is working Full Stack Developer / Tech Lead. Experience in building test automation from scratch for mobile, desktop, web projects (mainly for financial companies). He likes to participate in hackathons and work with smart colleagues. He conducted many interviews (more than 200, and has already stopped counting) for test automation engineers, developers, and analysts. The last few years working in the company Grid Dynamics. Now living in California, working on a contract with Google.

Flaky tests

Andrey Solntsev / Codeborne

Flaky tests - autotester headache. Yesterday the test was green, but today it suddenly turned red - for no reason at all. Nobody changed anything. Just the moon is in the wrong phase. Just the matrix is ​​joking at you.

We will analyze a bunch of real-world examples of flaky tests from my home collection. And let's figure out how to write tests so that they are stable and independent of the developer’s karma. , — , .

— Codeborne. Selenide, Devclub, . , , .

: Truths about technical testing

Alan Page /Unity

( ) « ». , — . , , , , - .

, , , . , .

Alan Page

25 . «How We Test Software at Microsoft» «Beautiful Testing and Experiences of Test Automation: Case Studies of Software Test Automation» . , , . «» «The A Word». Microsoft Windows 95, Windows, Internet Explorer Office Lync. , Microsoft . 2017 Microsoft Unity.

Conclusion

Now all information is available, allowing you to decide whether to watch an open broadcast. I hope the program turned out to be good, and you wanted to connect to us. Address broadcast you already know . 8-9 !