The point: the top 10 reports of Heisenbug 2018 Moscow

How to simplify refactoring? How to teach the developer to avoid typical errors in the UI? How to make the audience of a testing conference delighted if you are not a tester yourself?

By tradition, opening for everyone video of reports Heisenbug , we publish on Habré top-10, made on the basis of audience reviews. The reports in the post are arranged in an ascending rating: the difference between neighboring places is insignificant, so you should not give it a lot of value, but the main victors at the very end. Who were they this time?

---

Need to do a project refactoring? Have an IDEA!

Speaker: Artyom Eroshenko
Presentation of the report
')
IntelliJ IDEA is usually perceived as “where to code”, and not “what can be encoded.” But generally everyone can extend the IDE functionality with their own plugin - and Artyom Eroshenko described based on his own experience, which is good in the context of refactoring.

Artem is well known by his previous reports about the Allure Framework. In this case, everything is different: the word “Allure” can also be heard here, but not as the main topic of the speech, but only as one example (transition from the first version of Allure to the second).

---

Zelorochki in Selenium WebDriver

Speaker: Alexey Barantsev
Presentation of the report

There are already a lot of reports, tutorials and texts from various authors about such a popular tool like Selenium. But one thing is to listen to some speaker who owns this tool, and quite another is Alexey Barantsev, who has been participating in the development of Selenium WebDriver since 2011.

When you see any complex project from the inside, you understand a lot of things that are not obvious from the outside: for example, solutions that may seem strange to users show good reasons. And in this case, Alexei just talks about how the most "confused" situations are seen from within.

---

Recipes for creating from scratch and development of a load testing system

Speaker: Anatoly Plaskovsky
Presentation of the report

There are two things in people's ideas about load testing, with which Anatoly does not agree. One is when this activity is considered to be “nailed” to the subject area: it’s said that everything is so different with game devs and fintech that experience in one of these areas will be useless in another. Another is when the words “load testing” and “work on performance” begin to be used as synonyms.

And both of these disagreements are reflected in the report: we are talking here about general techniques that can be useful in very different areas, and from the words “workload” and “performance” carefully choose the appropriate context.

---

Testing systems with external dependencies: problems, solutions, Mountebank

Speaker: Andrey Glazkov
Presentation of the report

Dependencies generally complicate testing, but some cases can be especially intricate. What if your system must successfully interact with a stranger, which is being developed in parallel, and from a stranger you have neither code nor sufficiently complete data, but does it change in the process?

Andrei Glazkov encountered the intricate cases himself and spoke about the experience he had gained: starting with how imitation of the actions of external systems creates a division into “stupid” and “smart” fakes, and the problems that arise at the same time (“the code with which we we test, it becomes so complicated that bugs are already arising in it ”), and moving on to how problems were solved with the help of Mountebank.

---

Features of visual interface testing

Speaker: Anton Usmansky
Presentation of the report

Tools for comparing screenshots will help you to notice if something went wrong in the interface. But in search of this difference, they may find the screenshots different as well, where, from the point of view of the interfaces, everything remains the same. What are these cases and how to learn to reject them right away without wasting time? And what is the common situation when the automation signals a difference, but for the naked human eye, the screenshots look alike?

Anton Usmansky himself is engaged in the development of Gemini and Hermione tools at Yandex, but the report is not specifically about them, but about the general principles of operation of such projects. Earlier on the software-testing.ru appeared text version of this report.

---

Thousand and one UI-bug, or How to teach the developer to avoid typical errors in the UI

Speaker: Ekaterina Mikheeva
Presentation of the report

Thanks to a popular post about the number of Android devices required for testing, Habraw users can remember Ekaterina Mikheev . In her new report, Android fragmentation is also mentioned, but the context is different.

Sometimes testing UI is fascinating, and sometimes it is a routine fuss with stuffed teeth: the same errors occur again and again, and not so completely incomprehensible, and you spend time trying to fix it for the hundredth time. that "tsya / tsya". What are these mistakes and what to do to not deal with this anymore? How does this work affect the fact that sometimes people record someone on the phone as “Do not pick up the phone (deer)”? And how can a robo-eye come out of an eyebrow?

---

Rediscover exploratory testing

Speaker: Ingo Philipp
Presentation of the report

If the words "automation testing" managers can light up the eyes, then the words "exploratory testing" they can go out: not only can you not transfer the work to robots, it is also difficult to formalize the process, but how can you save company resources?

Ingo Philippe begins by asking why without this the company risks losing even more (“you can automate the verification of those risks that we know about, but not those that we don’t know about yet”), and then move on to how to live with it ( for example, what is done with the same process formalization). Probably, the audience’s assessments are partly related to the speaker’s ironic tone (“testing software is like washing a pig: a process without a clear beginning and end, where in the end you don’t understand why you got involved in this”).

---

Tester Voyeurism, or How User Observation Will Help You

Speaker: Antonina Hisametdinova
Presentation of the report

This report on interfaces and possible errors in them is already familiar to Habra: we previously made him a text version , so that you can not only watch it, but also read it. So instead of describing just give a few comments habrapovateley:

• “A delightful article. I don’t even know to whom it can be more useful - QA or design-representatives ”
• “Awesome post, nothing new, of course, but everything is gathered in one place and you can send people straight here, thank you”
• “It seems to me that this should be interesting for all developers who are at least confronted with user interfaces”

---

We have DevOps. Let's fire all testers

Speaker: Baruch Sadogursky
Presentation of the report

Baruha is well-known to visitors of our DevOops and Joker conferences, but testers saw it for the first time. Can a speech at the testing conference be good to take the floor, where the words “I'm not a tester” sound right at the beginning? As it turned out - more than.

Here it is necessary to make an important reservation: it was a keyout, that is, not a regular report in one of the three halls, but a speech that opened the conference for all viewers. Therefore, it was not about the details of a particular tool, but about industry trends. If the word “QA” is not in the word DevOps, then what does the widespread distribution of a devops mean for testers? Do they need to fear for their jobs, when developers are surprisingly actively writing tests themselves?

It is especially important for keyout that not only the material is good, but also the speaker is bright - and this is not to be taken away from Baruch, you will instantly recognize him from a thousand even by a loud voice, even by a colorful hat. And in the end, he won the love of testers, taking second place in this rating.

---

Extreme testing: tricks from the dark corners of mobile interfaces

Speaker: Vitaly Friedman
Presentation of the report

If the conference began with Baruch, then it ended with this performance, that is, both top lines of the rating were occupied by keynotes. In this case, like Baruch, the charisma and charm of the speaker play an enormous role, and he is also not a tester: Vitaly is the founder of the famous site for web developers / designers Smashing Magazine . When the site teaches others how to properly do interfaces, it is not surprising that he himself has been carefully thought out - so Vitali knows a lot about interfaces.

He has previously spoken at Heisenbug in St. Petersburg, and then gathered reviews like "this is not very testing, but it's amazing." And now I came to Moscow, and this time the material of the speech was different from the previous one - but there was no less enthusiasm.


For those who are dozens few, more videos Heisenbug 2018 Moscow - the link .

---

If you liked these reports, please note: May 17-18, the next Heisenbug will take place in St. Petersburg . In contrast to this, it will be possible not only to look at the reports, but also to personally ask questions to the speakers: each of them after his speech answers in detail in a special discussion area. Already available details about the program - on the website . Closer to the date, the program will become known more fully - but the price of tickets is gradually increasing, so buying them in advance is profitable. And now the last days of receiving applications for the report are coming, if you want not only “to see others”, but also “to show yourself” - respond!