Registration for Allure Server Meetup in St. Petersburg

We invite you to the Allure Server Meetup , which will be held on March 21 at the St. Petersburg office of Wrike.
Each testing department strives for speed and quality at speed. We in Wrike write a large number of autotests, run them as quickly as possible and at the same time strive to spend the minimum time on their support and documentation. We have been working with qameta.io for a long time on automation frameworks and tools. So, we have been testing the new TMS system - Allure.Server for more than a year, which fits well with our ideas about test documentation and autotest management. On the Allure.Server mitap, we will talk more about this system, usage patterns and technical implementations on top of this system.

In a programme:

Anton Bashkirov - Allure server: transformation of test case management in Wrike
')
I will talk about how we in Wrike with the help of Allure Server organized the process of creating test documentation on the principle “documentation from autotests“.

The usual documenting process might look like this: QA Manual writes a check list → writes test cases → gives them for automation → supports documentation as autotests change. We figured out how to simplify and cheapen this chain, thanks to the embedding of QA and QAA in the overall team flow of work, moving to a single documentation system.

We learn to use all the testing artifacts as documentation of our product, we actively use the autotest code annotations, linking them with the corresponding features in the server gait base, which allows us to work with test cases, check lists, autotests and even integration unit tests in a single ordered ecosystem .

Ivan Varivoda - Quarantine tests or how not to go crazy with 10K selenium tests

In test automation, unfortunately, situations are not uncommon when some autotests temporarily stop working correctly. Perhaps these are test flags or their infrastructural problem or bug has affected their performance - one way or another we have to “turn off” such tests from the launches or ignore them.

When there is a small number of tests in a project and they don’t chase often - there are no special problems, but with an increase in the number of tests and daily launches, it becomes imperative to turn off the broken tests as quickly as possible and be able to control the “turned off” tests.

We will talk about how to quickly “turn off” tests, what a test quarantine is, why it is needed, we will tell you how it works at Wrike, and where Allure Server is.

Discussion: Artyom Eroshenko, Mikhail Levin

In the format of the dialogue, which transfers questions from the audience, we will discuss the problems and directions of development of test management, interaction with Qameta and future plans for the Allure server.

We are waiting for you at the Wrike office on March 21 at 19:00.

check in