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

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.

Reducing end-to-end test execution time is critical for software development life cycles that wish to implement continuous integration and delivery. Selenium WebDriver allows us to run e2e tests on web applications in different browsers. As it runs across many browsers and operating systems, there are many possible capabilities to test. This workshop will help you to get started with the setup of dockerizing parallel execution of Selenium tests by cutting your test runtime up to 10 times. We’ll also look at how to run tests against several browsers and capabilities.

In these high-technology times, it is really hard to catch up with everything. Especially in the mobile world when there are thousands of mobile devices with different modifications of the Android OS. Most of us who work in the mobile testing industry are familiar with the Appium framework for UI automation and also aware of its complicated setup and complex maintenance. Using Docker in Android UI automation is making our life much easier. Docker-Android is a docker image built for everything related to Android mobile websites or application testing. All the tools needed (devices, framework, Android SDK, etc.) are packaged in the image. It is free and open source and supports other features, such as video recording. In this session, we will talk about the advantages and disadvantages of Appium and docker-android will go throw getting started with Docker-Android and run sample tests against it.

The origins of quality (assurance) engineering are in manufacturing, where quality engineers apply primary statistical methodologies to improve the quality and productivity of products and processes. In the past decade, people have discovered that these methodologies effectively improve almost any system or process, such as financial, health care, and software. Quality Engineering is embedded in Software Engineering and has a high impact and role on the SDLC. QE drives the quality development of products and processes while enabling effective testing in parallel. It has been changed over time and has different scopes starting from testing to automation. 

Let’s talk about the evolution of Quality Engineering and the future of our profession. I will share the ideas and approaches I have experienced during the last 12 years.

Parallel execution of test cases is one of the essential requirements of a modern test automation framework. 

Generally, to run Appium Suite in parallel, we use a selenium grid and distribute tests across multiple machines, reducing the time required for running tests. To run tests in parallel, we need to configure Selenium Grid with Hub and mobile devices. Running tests in parallel on an in-house device farm with Selenium Grid will help you run your suite a dozen times faster and help the product teams get fast feedback on any change.