Talks

From her own experience, Ekaterina will review the most common, but not really evident mistakes in developing Android interfaces and explain why they appear.

Liudmila will tell how UI team at Mail.Ru Group was implementing page layout regression testing, what were the premises for this decision, what challenges the team encountered and what problems managed to solve.

Spring 5 spreads across virtual machines, but the core project behind it — the Reactor project still isn't so popular and a lot of people don't know how to deal with it. This talk will give some insights about testability and debug aspects.

Kirill will talk about tests that help developers write code and verify already written code on an app level.

Contract testing is an alternative approach to testing microservices. We will see a minimal working example using Kotlin and Pact framework, explore how much you can gain depending on the effort you invest and take a wider look on the contract testing ecosystem, by comparing Pact with Spring Cloud Contract.

Ingo discusses specific heuristics and techniques of exploratory testing, especially useful in large-scale and fast-paced development environments, to get the most out of exploratory testing in your daily work. Learn that exploratory testing is not just error guessing or common bug hunting, but rather is at the heart of all things testing. Take away a highly productive approach that puts the adventure and effectiveness back into your testing.

Artem will tell about an API which can do refactoring, explain how it works and give several examples of migration (from Allure 1 to Allure 2, from jUnit4 to jUnit 5) and synchronization of the code and Jira tickets (test cases).

Vadim will tell how they at Mail.Ru Group approach unit testing for their projects. He will cover not only how they do it, but also how they view it.

Liliia will tell how they do QA for all the infrastructure around Kotlin in IDE (and not only in it) and how do they manage with an open tracker where everyone interested could write to.

This talk will focus on security from the point of view of software testers, not security experts. It will focus on tools and areas of testing which are often forgotten and could lead to security vulnerabilities. All of this is nicely peppered with examples from the open source world, some of them coming from Red Hat's own backyard.

By observing users, you can get an idea how people use the services in real life, which can help you to find and fix previously unknown mistakes.

Challenges in development of Selenium WebDriver and how Alexey and his colleagues overcame them.

We'll talk about how iPhone, the brick and year 1970 are connected. Why the state-of-the-art Google Pixel 3 suddenly grew another notch and calling 911 caused OnePlus 5 to reboot.

Anton will tell what you should pay attention to while coding, choosing and using a visual regression testing tool.

We will walk through steps to diagnose network performance bottlenecks in mobile services. Attendees will leave this talk armed with the tools to test, diagnose and resolve the top network performance issues that affect mobile today.

Ekaterina will tell how they were "leveling up" their low-level frameworks, making test projects more flexible and scalable.

Description will be announcedDuring transition from Quality Engineering team to Engineering Productivity team, it's very critical to design and build efficient test infrastructure and toolchain ecosystem from engineering productivity perspective. Following this, this lecture will discuss several engineering best practices.

We'll discuss a system testing approach for platform consisting of several microservices. We run our services in Docker containers, using TestContainers library and JUnit 5 framework. For each service we create JUnit 5 Extension, so the respective container can be lifted by simply putting an annotation in the beginning of the test. Adding and removing annotations, you could write quite elegant tests both for one service, the subsystem, and for the whole platform.

We'll show how to deploy a scalable Selenium cluster, using Selenoid, write your own Mesos framework on Go even if you only know Java, deploy it in the Mesos cluster and not get disappointed in humanity.

In the age of single-page web apps, memory leaks in JS became the ultimate bane. Sergey will tell how in Tensor they test their products for memory leaks.

Anatolii will tell about building from scratch and supporting load testing system with a few limitations of financial organisation. This talk will be useful both for those who only start to (or want to start) look into load testing and for those who've already built working system in their company and want to improve it.

High-level view of languages and frameworks commonly used to build blockchain applications, with a focus on Solidity (the language used for Ethereum applications). This talk highlights a checklist of common vulnerabilities and provides advice about how to guard against them.

Insights into how to get started with a successful integration of artificial intelligence in your development process.

End-to-end tests of mobile applications are slow tests. Multiple end-to-end tests for mobile applications — it's very slow. Is it possible to run mobile tests faster? In this talk, we'll use profiling to find bottlenecks in test code.

Baruch will tell us if it's true and DevOps will take away our bread and butter or we still need to keep fighting.

Leonid will tell about what Terraform is as a tool, how it can simplify deployment and support of the Selenoid cluster, and how Telegraf + InfluxDB + Grafana can help in monitoring the cluster's condition (Terraform is also involved).

We will demonstrate the benefits of static code analysis tools on practical examples. There is a number of errors, which can be hardly found using other methods. And such errors will be showcased in abundance. We invite developers and testers to evaluate all of the power and beauty of static code analysis methodology.

Andrey will show how to solve problems of external dependencies testing with mocking, share best practices of using mocks in manual and auto testing, explain how to embed mock system into an auto testing framework.

Vitaly will be taking a microscopic examination of common interaction patterns and interface components appearing and tested in mobile interfaces. We'll look into onboarding issues, the infamous hamburger icon, strange carousels, complex data visualization and feature comparison.

Learn how to implement monitoring features in your code so you can surface issues that only appear in the real production environment.