What's new in automated testing approaches? We find out March 15 in St. Petersburg

Published on March 06, 2017

What's new in automated testing approaches? We find out March 15 in St. Petersburg



    Next week, on March 15, a meeting on automated testing will be held in the St. Petersburg office of Wrike . The meeting will be devoted to a review of new effective approaches and tools in the field of test automation. We will evaluate their applicability in various cases, try to give specific advice and recommendations on how they can be applicable to your specific tasks. Experts will be happy to answer your questions. The meeting will be interesting for both automatic testing specialists and developers who write autotests.

    Program and registration.

    Program:


    1. Oleg Nikolenko, QA Automation Team Lead, Wrike

    HtmlElements - And the tests have layers

    Let's talk about the costs of automating web tests, such as code support, blinking and slow tests, unreadable reports. I will share how we solved our problems and what tools we used. I’ll tell you about the latest changes in the htmlelements library, about how our PageObject now looks, what layers our tests are made of, where we divided xPath getters and what extentions for elements are.

    2. Kirill Merkushev, head of the group of automation of development and testing processes, Yandex

    Code Generation as a way to solve the problems of the automator

    Test automation is not just about writing WebDriver tests. This is primarily a solution to regularly arising problems, or optimization of repetitive labor.

    In order to write high-quality, supported tests and utilities for testing, many additional costs are required - http clients, organization of checks, description of the project with tests, documentation support (this list is much longer!).

    In the report, I’ll talk about how you can automate code writing that eases the burden of supporting additional code for tests, what ready-made tools and mechanisms exist in the Java ecosystem and what we use to turn a dozen lines of declarative descriptions into hundreds of lines of code that you can simply take and use .

    3. Artem Eroshenko, senior engineer test automation Yandeks.Vertikali

    Selenium: new hope

    every developer who writes the tests via a web-interface, familiar tool called Selenium. When there are a lot of tests, it becomes necessary to manage browsers using the Selenium HUB.

    Unfortunately, the standard Selenium HUB has many drawbacks. In the report, I will tell you how to quickly and easily raise a high-performance and reliable Selenium hub using an open source tool called Selenoid. The peculiarity of this tool is that a separate docker container starts for each browser session. This allows you to ensure the purity and isolation of your sessions and saves you from many infrastructure problems.

    4. QA section with speakers

    Moderator - Mikhail Levin, QA director, Wrike

    Register

    Watch online