In this talk, Adam will discuss the different types of risk that you should be considering (technical, business, etc.) and how you can use the assessment of risk to create a test plan that gives you the greatest risk coverage in the time available.

There seems to be a very wrong perception of conducting load testing. Many think it is understanding a performance testing tool and running a few tests. Seldom is serious thought put into creating tests that actually add value and create an impact on the actual testing. This requires a lot of strategy and planning that goes into creating the Perfect load and this talk will cover all the soft skills that a test engineer requires to get the job done.

“There is a bug in production” have been the scariest words for Elena as a tester and QA analyst. She was sweating, blushing, panicking. What made it worse is that these bugs were often brought by the 3rd parties SDKs, so she didn’t have full control over this part of the code herself. Her attitude towards bugs in production changed after she observed a team of firefighters at work.

In this talk, we will touch on why it is important, demystify few myths about continuous deployment, and emphasize key areas which will allow us to gain that capability and be more effective at delivering the software.

In this talk, we’ll discuss methods used to ensure everything works the way it should before deploying to production.

When things go wrong we try to do better. Incident Analysis, Root Cause Analysis, and Post Mortems are an important part of continuous improvement and many of our workflows. We’re going to look at what we do when things go wrong and the really easy things we can do to make things worse.

ART – Autonomous Real-time Testing is a concept for modern software and system testing in the area of Digitalization. It unites three approaches, that you will learn about in this session. This presentation outlines the current state of availability of tools.

In his presentation, Wim is going to explore the idea of a tester doing the requirement engineering, or the inverse of a requirement engineer doing the testing. He will explain how requirements elicitation techniques, such as paradox brainstorming and 6 thinking hats can be beneficial for the tester, but also how to test techniques, such as Decision Tables, can ensure a higher quality of requirements.

But wait, this talk is for QA Engineers, where is their place in this process? Will it mean they will never write tests again? There will be a huge room for their work. Yevheniia believes QA is the best person to make such changes happen and continue working along the way. She wants to show how moving e2e tests writing to developers can become a next-level task for QA engineers.

В рамках доклада Георгий расскажет о подходе к созданию объектов, использующем базу данных в качестве основного и, иногда, единственного места которое знает “что и как” создается. А также о том как подобный подход к созданию объектов облегчает и ускоряет написание автотестов в SOAP-UI И автотестов в Java На веб-сервисы.