Talks

The talk will discuss common flaws in systems written in Angular: why they occur, how to find and test them. General recommendations for safe programming and testing will be given.

Panel discussion is not recorded Today everyone wants to make releases faster, but companies’ staff is always limited. In this discussion, we will talk about whether teaching automation to manual testers is worth it and whether the time spent on this process will be profitable for the company. And what aspects should the teaching process start from.

In this talk, Artem wants to take one automator with 100 autotests and using consecutive degradations turn it into the testing department that will do the same job. With this experiment, we will be able to understand where the time goes during the testing process.

Microservices is good stuff for deployment and development, but it’s bringing some challenges for testing. The contract testing approach will help and in this workshop, you can learn more about that.

Together with Iakiv we'll define the requirements for the main features for a minimal framework based on Selenium Webdriver for high-level system UI tests (with examples in Python). We'll analyze the main API styles of these frameworks and mainly the Selenide/Selene style. And also consider when it's more flexible to build our solution and when it's simpler to use an existing library.

Within 2 hours we will analyze the architecture and write in Python from scratch the core of a wrapper around Selenium Webdriver with API in the style of Selenide/Selene, along the way, focusing on the usefulness of all added features, and why what is already available in Selenium WebDriver is not enough for effective implementation of high-level user-oriented UI tests.

Maria will talk about the experience of autotesting in Flutter, why and for what these types of autotests are needed.

At Ozon Mobile QA engineers usually act as release engineers.This helps them speed up development and testing processes, as well as build expertise that is not typical of QA engineers. Daria will tell about one of such features, the automated creation of a Merge Request.

Daria will talk about the difficulties which you may face when working with an unusual product, and also what steps from the experience of her team you may take when trying any new feature.

We'll talk about Pipeline static analysis, unit and integrated testing, CI/CD for Jenkins Pipeline... with help of Jenkins Pipeline.

Many people think that testers need to write E2E tests and nothing else. This is what happens in many teams. But how correct is this in 2021, when you hear about DevOps, Docker, TestOps, CI/CD, and other "odd" things? How right is it not to use the infrastructure and experience of colleagues in the shop?

How to spend less time on writing typical tests in Postman, generate tests automatically (not data for tests, but tests themselves), and make updating of test collection way easier when API changes occur.

Aleksandr will share his experience in working with the safety-critical software and the explain the reasons why both its testing and verification processes are significantly different from the ones used for other types of software. Another subject worth considering is reduction of cost and time efficiency by implementing shrewd planning and forward-looking approach in automatization.

A short talk about the practical use of openAPI Generator:

• how openAPI Generator works, and what options there are for influencing the final result;
• options of customization of the openAPI Generator;
• What problems you might encounter in the process, and options for solving them.

The talk will take 15 minutes, in the process there will be examples of code on Github.

Let's talk about the overlap in testing approaches and methods unique to each industry. We will discuss not only the problems and tools, but also the composition of the teams testing the solution.

Program committee members often attend conferences and watch papers, facing the agony of choosing participants.

In this session they will answer the questions:

• how to prepare for attending a conference?
• What should be paid attention to when choosing speakers?
• How to get the maximum benefit from participation in the conference?

Anna will answer all questions about code quality on legacy applications by showing how these problems were solved on real-world projects.

Panel discussion is not recorded!

And the problems are still the same... Let's talk about common issues with leads:

1. Is it okay for a testing lead not to test?
2. Who should the team development initiative come from?
3. How to live with imposter syndrome?

Within 2 hours we will analyze the architecture and write in Python from scratch the core of a wrapper around Selenium Webdriver with API in the style of Selenide/Selene, along the way, focusing on the usefulness of all added features, and why what is already available in Selenium WebDriver is not enough for effective implementation of high-level user-oriented UI tests.

Panel discussion is not recorded!

Denis Kosarev, Senior Project Manager in Luxoft, will share his experience in preparing and passing job interviews successfully, tell the audience about the most common tasks and give some advice about what to ask about your future team and work.

Elizaveta Kuznetsova, Lead Recruiting Specialist, will make some talk about the good and bad practices in preparing for the job interview and provide the participants with subtle aspects of rocking an interview in Luxoft.

A story about how fuzzing testing works, what's inside it and how it all works together.

Modern banks are ready to experiment, but one has to understand possible benefits and risks from applying new approaches, like TCR.

To what extent TCR is OK for your team and project? What to expect from it? What teams need to be careful when choosing TCR?

Guys are going to talk about this during a short, but rich discussion.

Today, all large corporations are building ecosystems not only using desktop applications but also using connected devices. Automotive solutions are one of them. In this talk, Aleksandr will tell about what kind of automotive solutions exist, what structure they have, and how to test them.

In this workshop, we'll follow all the steps of writing tests from scratch, and solve the problems. Then we'll see how the tests behave when the code changes, improve logging for ease of debugging and discuss ideas for further development of the approach.

Panel discussion is not recorded

• How to raise issues in some project
• When it's worth contributing and when it's not
• How to find a task in a particular opensource project
• How to create pull request and communicate with maintainers team, so that your pull request goes to release

Live from Heisenbug's main studio.

We'll talk about Pipeline static analysis, unit and integrated testing, CI/CD for Jenkins Pipeline... with help of Jenkins Pipeline.

Discussing security issues

Liubomir will tell about how the drone sees the world, about tests on various road surfaces, AR in tests, and what else such a platform is needed for.

The world of testing is diverse and is not limited to testing mobile and web applications. In this short session we will try to open the door to the wide world of hardware QA, briefly get acquainted with the tasks that our engineers face every day, with the specifics of our work, and try to show what is the testing of storage systems.

Everything seems clear with testing web site, mobile app or even game — there are many people who do this and are ready to share their experience, what about database, particularly distributed one?

Testing giants like Apache Ignite seems to Anton a topic which is not often discussed, and he decided to share the details of Sber experience in his talk.

Few testers remember about exploratory testing: in the talk we'll find out what it is, why it's needed, is it really necessary and how to organize it, if you also want to try it.

Financial organizations are actively developing performance testing. And so it will be interesting to compare approaches and technologies used in different teams. Vyacheslav (VTB) and Maxim (Tinkoff) will talk about their experiences with the bank.

Evgeny will tell what happened with the popular testing tool — Protractor and show what problems you may face when switching to WebdriverIO or Playwright.

Several techniques of the Declarative approach to the Test Design will be present during this report. One of the possible Architecture solutions of the Test Automation Framework with support of MBT/MVVN will be provided.

There are more and more companies on the market that are starting to develop or have already launched their hardware products. Roman and Oleg will share their experience in testing smart devices at various stages of their development.

The session will be useful both for those who have been familiar with testing for a long time and for those who are just starting their careers in this field.

At the workshop, Artem will build a simple application in Java+TS and cover it with a set of various tests.

Panel discussion is not recorded!

We'll talk about how deep engineer should dive into development and why the industry needs QA engineers instead of testers. We'll also talk about when QA engineer may and should take part in the development and how it works in Raiffeisen.

We will talk about the schedule, sessions, and share the information. Join the broadcast to find out what's on the air soon!

This talk is about how to prepare data for tests. Dmitry will use the example of Ozon integration testing to show how we prepare states for different environments.

The authors will tell you what not to do and why not to do it. And most importantly, they will give two reasoned points of view on controversial points!

Playwright Test runner is a new Node.js test runner for end-to-end tests from Playwright team. In this talk, we'll get an introduction to Playwright Test.

In this session, members of the program committee will dispel myths and explain how papers get on the conference program.

Learn how Drill4J enables you to run tests quicker, keep them relevant and save precious time - walkthrough based on Cypress tests for React application.

Certification is the next step after the basic certifications in the direction of Agile. The talk will cover:

• the release of the first incremental certification;
• why the new direction Agility at Scale was chosen;
• the modern approach to quality management;
• why it is important to create a quality culture in teams and the organization.

Live from Heisenbug's main studio.

Microservices is good stuff for deployment and development, but it’s bringing some challenges for testing. The contract testing approach will help and in this workshop, you can learn more about that.

A story of developing an all-in-one test station in production — the last step before packaging the device and sending it for sale.

How to build mobile UI test automation from the scratch and include it in CI pipeline.

We take stock, remember the bright moments and talk about our plans. Join the broadcast, so you don't miss anything!

Mikhail will tell the business case of ExoAtlet project: where dreams may lead, what difficulties startup face deciding to develop hardware, and how the meaningful condition helps not to give up and overcome obstacles.

Testing tools seem to focus on throughput: how many tests can we run per unit time? Kent suggest an alternative: mean time to first failure. How long does a programmer have to wait until seeing a test fail (in the case that one fails)?

In this talk, Aleksandr will tell on examples of why and for what we use plugins. What parts of functionality do we put into plugins and what do we leave in the framework.

Simple and complex, local and cloud, free and expensive - which CI do you use and why? What others are out there? What's worth trying? Where is it all going? Let's try to figure it out in our Zoom session.

Dmitry and Nadezhda will share their systematic approach to the analysis of the flaky tests caused by various reasons and will tell you how to prevent the appearance of flaky tests.

We'll discuss the pillars of a valuable unit test and when you should and shouldn't use mocks.