Code Generation, Selenoid, HtmlElements in the auto-tester

On March 15, a meeting of auto testers took place at the St. Petersburg office of Wrike. We talked about new effective approaches and tools in the field of test automation, evaluated their applicability in various cases, and we hasten to share a record of reports and presentations.


')
Oleg Nikolenko, QA Automation Team Lead, Wrike - HtmlElements - And tests have layers



Let's talk about the costs of automating web tests, such as code support, flashing 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 insights in the htmlelements library, how our PageObject now looks, what layers our tests consist of, where we shared xPath getters, and what extentions are for elements.



2. Kirill Merkushev, Yandex - Code Generation as a Way to Solve Automator Problems



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

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

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



3. Artem Eroshenko, Yandex. Verticals - Selenium: a new hope



Each developer who writes tests through the web interface is familiar with a tool called Selenium. When there are a lot of tests, there is a need to control browsers with the help of Selenium HUB.

Unfortunately, the standard Selenium HUB has many drawbacks. In the report, I will tell you how you can quickly and simply raise a high-performance and reliable hub of Seleniums with 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 guarantee the purity and isolation of your sessions and saves you from many infrastructure problems.