Archive for January, 2019

Let’s talk about most known device farms: Bitbar, Kobiton, Saurcelabs, AWS device farm. I’ll observe the following topics:

– proc & cons;
– parallelism and how it is organized on device cloud platform;
– how CI/CD process can be organized with this device cloud platform;
– what reporting tools devices cloud platforms provide.

The idea is to show more complex test automation architecture which goes beyond the ordinary arrange->act->assert or set-up->run tests->tear-down workflow. I’m going to show you working example, how can you test MapReduce jobs’ logic and REST APIs in a transparent, robust manner by using high-level logical abstractions in test automation framework via Jenkins pipeline. Will be shown with Kotlin + Gradle + JUnit + Jenkins pipeline as code.

2018 was another year full of updates in mobile testing area. Appium finally released Espresso Driver, migrated to W3C protocol, added find by image functionally and even exposed integration for custom plugins for element search, that anybody can develop and use.

On the other side, Google released AndroidX Test, open-sourced set of cross platform APIs that should make native test framework attractive as never before. Apple gave a speed boost with Parallel Distributed Testing in Xcode 10 and several cloud providers launch XCUITest support on real devices. Does Appium have anything left to oppose native test frameworks? Do Espresso/XCUITest still have any weakness?

I would like to address these questions and compare current state of each framework, its functionality, revive weakness and points to consider while selecting any of them.

As a Test Automation Architect have you ever solved the following problems (in the scope of testing a web application):

– impossible to work with file system on the server side (when SSH is unavailable or is the reason of tests flakiness);
– chaos in developing and maintaining of mocks/stubs for integration testing with 3rd-party systems;
– developers refuse to expose API that is needed only for testing.

I will describe the TAA approach of having a web application for testing needs that could resolve these and other problems. We will call this application QA Web Services and deploy it on the same server/container as the SUT.

We will consider benefits and drawbacks of the approach, go through useful tips. The target audience is Senior+ test automation engineers and Solution architects, basically it would be useful for anyone who wants to enhance the automation infrastructure, so that all team members would win.

I’d like to share expertise of using Selenium and Jenkins clusters deployed in Kubernetes based on AWS. I will explain how Kubernetes helps to scale infrastructure and save budgets for cloud services.

Will share my experience how to build an automation solution based on Appium that provides a possibility to run same mobile automation tests on both iOS and Android platforms. Also, going to show how to integrate mobile automation into a main development process, will include useful tips & tricks for mobile automation on real devices and practical demonstrations with code sharing.

There is a lot of tools for UI automation in JavaScript – Cypress, Protractor, WebdriverIO, SelenideJS…

When you decide to do ui automation, you need to choose most flexible, maintainable, powerfull tool which can provide you reliable test results.

So…which one? 🙂

In the test automation industry, the Page Object pattern has been used for more than 8 years. During this time, Java has been updated from JDK7 to JDK11. It’s time to update the Page Object pattern. Atlas – Next Generation of Page Object, which uses the interfaces instead of classes, Page Object tree structure, embedded waits and clear assertions. In talk, I will tell about the core functionality of the framework, the developer, which I am and show it extension points. I will also demonstrate how to use one PageObject for two platform: IOS & Android without boilerplate code.

Acceptance tests are crucial for success of any software project. Automation of acceptance testing significantly reduces the feedback loop, allowing to release faster and more frequently.

However there is one problem. Automated tests are written using programming languages and rarely can be easily read by non-technical stakeholders. There have been some attempts made to remove this gap, like Gherkin language, but it’s support might be very expensive and not pleasant for developers.

In this talk Serhiy will present Canopy – an F# DSL around WebDriver. It allows to describe acceptance scenarios in a form that could be easily understood by everyone. More than that, it also makes programming tests a joy, because it’s pure functional language and developers would get opportunity to try functional stuff on their work.

Modern web application testing is a hard and ungrateful job. But may be this is just because we still don’t have great tool for testing, that could be our friend not enemy? In this talk I will present you Cypress.io – free test runner made without Selenium or WebDriver. With Cypress you could make your tests quick, simple and useful. Short summary:

– setup and your first test;
– architecture and main capabilities;
– async code testing, components and API requests;
– run on CI/CD server;
– end of Page Objects with App Actions usage.

AI-powered chatbots and voice assistants are still emerging technologies, but they’re starting to gain traction in the workplace, as well as at home. Like any other software, such smart assistants have to be well-tested to ensure they meet people’s needs. But how can we test something so human-like?

In this talk, I’ll share my experience in voice assistant/chatbot development. Besides the general info about the technical stack, bot’s internals, challenges, and the existing test automation tools and frameworks, you’ll see several practical examples, based on Web, API and Voice interfaces.

People often think that running parallel tests in JavaScript is hard, and actually it is. We will explore possible ways of running JavaScript(nodejs) tests simultaneously using different approaches starting from basic and well-known splitting by files, and finishing with some crazy experimental things like worker threads, Functions as a Service, Isolates. Explanations and performance metrics are included!

Record and playback tools like Selenium IDE have a stigma attached to them in our industry — they’re not worth your time, they produce tests that are impossible to maintain, and they’re only for non-technical people.

But with the new Selenium IDE, that’s all just a bad rap.

In this talk Dave Haeffner will squash the stigma by showing you examples of how Selenium IDE can reliably augment and level-up your testing practice regardless of your team’s test automation maturity or your level of technical experience. He’ll also share how he went from a record-and-playback naysayer to a Selenium IDE maintainer.

Artem works as a team leader for several test automation teams, and he often has to deal with code refactoring in bulk. When developing a plug-in for IDEA he noticed an API which can do refactoring. This API’s strength is that we know everything about the code we work with: all kinds of the variables and classes usage, annotations signature, etc. Artem got an idea to make plug-in which will ease the project refactoring when switching from one version of the library to another.

In this session, Artem will tell how this API works and give several examples of migration (from Allure 1 to Allure 2, from jUnit4 to jUnit 5) and synchronization of the code and Jira tickets (test cases).

Multiplayer games are complex systems that contains different sub-systems like: server that process all logic, platform that is responsible for users and their data, clients that may run in different platforms.Sounds like a general enterprise application, but with difference that all these things are combined into one single game where players can play with each others and everything is focused on users’ satisfaction. So priorities are different.

But organizing automated testing of a game is not a easy thing. Lack of technologies and information at stackoverflow are just the beginning of upcoming pain.

I will talk how we organized automated testing of such game, how our pyramid looks like, what challenges we met and what solutions we made.

With this talk i will sanctify Test Data Management process: sub-processes, goals, benefits, stages. Share approaches at different scale, and describe the case how to build TDM at small scale, utilizing open source stack.

The talk will be about building integration testing approach for microservices architecture, building contract based approach as a layer of integration testing between the services. Also I’ll share how it can also be applied to UI testing, when we separate UI from backend and then use just regular Selenium for UI verifications, as well as to client side performance testing. This will be a success story with real achievements and challenges described, lessons learned and where to start if you want to reorganize your testing pyramid into a perfect one and have tests pass rate almost 100%.

During my career as a test engineer I saw many different approaches to manage test cases. Many of them were written manually and stored in some test case managements system. In this talk I will share real experience of the team that tried to manage test cases as a code.