Hi, I’m Sargis Sargsyan
a Developer. Engineering Lover. Quality Engineer. Developer.

Madrid, Spain

UI testing tools offer a robust solution for web application assessment, yet it faces a bottleneck when scaling up to handle extensive UI test suites that require hours to complete. This comprehensive workshop addresses this challenge by guiding you through the creation and deployment of a dockerized Selenium grid, enhanced with autoscaling and video recording features. Capable of efficiently executing several thousand tests in limited period of time, this advanced setup optimizes speed and reliability for UI tests.
Our deep dive will cover the strategic implementation of a high-performance Selenium grid, leveraging cloud technology for dynamic resource allocation and nuanced insight into each test. We’ll be grounding our discussion in a practical context, showcasing a real-world application of a robust UI test ecosystem with multiple nodes to operate tests in isolated environments. This approach not only enhances test accuracy by eliminating external interference but also offers a scalable and efficient methodology applicable to both existing and new UI test suites. Furthermore, we will explore how this same test infrastructure can be seamlessly adapted to run Selenium or Playwright tests in parallel, highlighting its adaptability and efficiency across different testing frameworks. By the end of this session, you’ll be equipped with the knowledge to revolutionize your UI testing strategy, making it more resilient, faster, and smarter, regardless of the testing framework employed.

Madrid, Spain

Big things do come in small packages, and end-to-end atomic tests are no exception. By focusing on a single feature and reducing the size of the tests, we can achieve fast, focused, and reliable feedback from our end-to-end automation tests. In this talk, we will explore the advantages of atomic tests and how they can solve common problems like unreliable test results, slow tests, and hard-to-debug tests. Additionally, Sargis will show real-world examples of the benefits of atomic testing through a case study that resulted in a multiple-time reduction in test suite execution time. Join Sargis to discover the power of atomic automated tests and take your test automation to the next level.”

Berlin, Germany

Big things do come in small packages, and end-to-end atomic tests are no exception. By focusing on a single feature and reducing the size of the tests, we can achieve fast, focused, and reliable feedback from our end-to-end automation tests. In this talk, we will explore the advantages of atomic tests and how they can solve common problems like unreliable test results, slow tests, and hard-to-debug tests. Additionally, Sargis will show real-world examples of the benefits of atomic testing through a case study that resulted in a multiple-time reduction in test suite execution time. Join Sargis to discover the power of atomic automated tests and take your test automation to the next level.”

Big things do come in small packages, and end-to-end atomic tests are no exception. By focusing on a single feature and reducing the size of the tests, we can achieve fast, focused, and reliable feedback from our end-to-end automation tests. In this talk, we will explore the advantages of atomic tests and how they can solve common problems like unreliable test results, slow tests, and hard-to-debug tests. Additionally, Sargis will show real-world examples of the benefits of atomic testing through a case study that resulted in a multiple-time reduction in test suite execution time. Join Sargis to discover the power of atomic automated tests and take your test automation to the next level.”

Big things do come in small packages, and end-to-end atomic tests are no exception. By focusing on a single feature and reducing the size of the tests, we can achieve fast, focused, and reliable feedback from our end-to-end automation tests. In this talk, we will explore the advantages of atomic tests and how they can solve common problems like unreliable test results, slow tests, and hard-to-debug tests. Additionally, Sargis will show real-world examples of the benefits of atomic testing through a case study that resulted in a multiple-time reduction in test suite execution time. Join Sargis to discover the power of atomic automated tests and take your test automation to the next level.”

Parallel execution of test cases is one of the important requirements of a modern test automation framework. Generally, to run Selenium Suite in parallel, we use a selenium grid and distribute tests across multiple machines, which will reduce the time required for running tests. To run tests in parallel, we need to configure Selenium Grid with Hub and Nodes, where the hub is the central point that will receive test requests along with configurations or capabilities. Based on the request received, the hub will distribute tests to the registered nodes. Selenium has made a set of Docker images that are available on Docker Hub. We have Selenium Grid and the browser images – Chrome and Firefox. There are also images with the debug versions, allowing us to view the test execution. Also, we will compare the Selenium docker with other solutions like Selenoid, Go Grid Router, and Zalenium and will throw advantages and disadvantages. In this session, we will go through the Selenium tests parallel run setup and configuration.

Performance is one of the main painful areas of UI test suits. Usually, engineers try to log in, logout, navigate, create data, execute an action from the UI via Selenium, then, in the end, perform test assertions. This creates serious performance issues for the Selenium suite and makes Selenium tests more brittle. We could face fewer problems if the test data creation and deletion were done before the UI test started the run. This will help to create independent tests later to be able to run them in parallel.
The workshop will help participants to create an automation framework that will be fast, stable, and reliable. The solution will work for new and existing frameworks. During the workshop, we will code together to create a  framework that will run UI tests in parallel with intelligent test data preparation. We will use Java, TestNG, Selenium, and Docker.

Performance is one of the main painful areas of Selenium suits. Usually, engineers try to log in, log out, navigate, create data, execute an action from the UI via Selenium, then, in the end, perform test assertions. This creates serious performance issues for the Selenium suite and makes Selenium tests more brittle. Also, the problem solution could be better if the test data creation and deletion also will be done before Selenium opens the browser. This will help to create independent tests later to be able to run them in parallel.

Performance is one of the main painful areas of the Selenium test. One of the most critical improvement points is Test Data creation and cleanup. In this talk, we will discuss how to create test data via HTTP requests and clean it after the test run.

Optimization of the Selenium suite is essential for us. In this talk, I will present how to create an HTTP requests builder to create and clean up test data after the Selenium test run. This will help you to prepare particular situation before logging into the web application via Selenium and testing the exact functionality you need. After the test run, the cleanup should be done again with an HTTP request to avoid performance issues and minimize flakiness for other tests in the suite.  

In addition, I will also present how to use HTTP code to set up session cookies and make configurations, then extract cookies and pass them to Selenium, which will help to skip logging in from UI for every test.