Archive for January, 2017

Almost all systems actively integrate with external services. Some of these external dependencies are legacy and slow, while some are modern and fast. Problems occur when we want to test our system in an isolated predictable environment. This is very important because in the opposite case, tests become flaky and unreliable causing the effectiveness of testing to decrease very quickly. Therefore, when testing is done with real external dependencies, the following factors could affect it: network issues, slow responses, unexpected failures, data corruption, access issues, etc. This tends to occur more often when external systems are legacy. Every programmer has to face legacy code day after day. It might be ugly, it might look scary, and it has even been known to make a grown man cry. Creating automation testing in cases like these can easily turn your testing into a nightmare.

The first thing that can help is writing stubs for external dependencies and using them for testing purposes. Another problem arises immediately: stubs fix external behaviour and nobody can guarantee that it will remain the same forever, especially if the service is under active development. Because of this, you need not only to have stubs written but also to regularly inspect changes in behaviour and adapt them. These activities significantly increase our development efforts in the testing area. Of course, such stubs should be able to work with legacy SOAP-based systems.

This presentation shows The Smart Stub as one of the solutions to simplify your life and make testing great again. Here are a few scenarios where The Smart Stub can be used. The Smart Stub can be used for local needs and on the CI pipeline as well, allowing for automation of the following activities.

– Running existing tests using The Smart Stub as a proxy to record all request and response pairs.
– Creating flexible matching rules for requests based on recorded data.
– Customizing responses with flexible data replacement rules to ensure they’re always up-to-date.
– Using The Smart Stub in replay mode when all matched requests are processed by The Smart Stub and actualized recorded response is returned. All non-matched requests are passed through and recorded for future usage.
– Recording request and response pairs could be scheduled for comparison to real service in order to detect changes in external behaviour as quickly as possible.

We all run tests on safe, separate test environments. But what if let them loose on production systems? Is that dangerous, or is it worth the risk? This can seem daunting, but there are huge benefits. I’ll discuss some of the downsides to testing in isolated, unrepresentative test environments, before talking about my experiences of using Selenium to test in production as much as possible. I’ll demonstrate the benefits, like how we can turn automated tests into monitoring and early alerting systems for our production environments, and the steps we need to take to make sure our production tests don’t affect our users.

Have you ever wondered how to test a light switch? Can you imagine it being one of the biggest challenges in your career? There are nearly six billion IoT (Internet of Things) devices. By 2020, this number may triple. Undoubtedly, it is a rapidly developing area of IT market.

I will take the participants for a journey to the IoT world. It will be a talk about the challenges that any tester will face at some point. I will present the dangers and snares but also good practices and practical approach to E2E test automation for the IoT solutions.

The main question is: how to test application for end user among so much hardware equipment? Technical examples will be presented using Python languages and supported by physical devices.

First thing that comes to mind if you think about patterns in test automation is Page Object pattern. Almost all know it and almost all use it, but it’s not the only software development pattern, that you can use in your test automation suites making them flexible and maintainable.

I would like to focus on two subjects. First show how to extend Page Object pattern and design your pages using factories and using how use entities in your tests in order to facilitate your assertions and make them clear and meaningful. Beneath that I would like to present how benefit from command and builders in your test code.

Technologies like Squarespace, Salesforce, WordPress, or WIX are extremely popular for those who want to create a working website without necessary developer knowledge. In this talk, I would explore how Salesforce uses Page Object Model patterns to test its Communities platform which is used to develop websites for Salesforce users.

Throughout the talk, we will explore how multi-frame platform can be directly mapped to POM for Selenium Webdriver, and how client side code is developed to support this pattern.

The importance and complexity of these test framework is that it needs to be applicable for both platform and produced websites.

In agile software development world, we are dealing with many test tasks such as user story testing, exploratory testing, check-list based testing, regression testing, performance testing, security testing in each sprint. Besides these testing activities, one of the test types which is considerably getting crucial is visual regression testing.

Visual regression testing focuses on to check visual contents and animations, page layout, and responsive design of a website/app. Because of the limits of human vision, human-based visual regression testing is generally error-prone and cumbersome. Hence, automation is inevitable. It enables us to run the tests much more precisely in a short time period. Also, it saves us a significant amount of time to deal with other manual test activities in each sprint.

In this talk, we will walk through well-known open-source and commercial solutions for visual test automation. We will learn which technologies they use, what type of visual tests they are suitable for, and their major differences between each other. Besides this overview, we will also make a real-life visual test automation demo by using Selenium, ImageMagick, and AShot.

If you think about tests rather than corn flakes whenever you hear the term “Flaky”, this talk might be for you.

I’ll share some thoughts about the relationship between quality and culture, the battle of manual VS. automation, and the notion of test pyramid. In addition, I’ll describe how we bake quality into products and processes at Google.

We passed a rapid path from manual testing and automated tests in Java as a separate codebase, which was being developed by a dedicated QA team, to the functional tests in JavaScript which are versioned with a project source code and are being developed by project developers.

I want to tell you why we had to create our own testing tools Gemini for visual regression testing and Hermione for functional testing. What challenges we faced and how we solved them.

Now everyone can follow our footsteps.

With more breaking points and less stability, E2E tests are very hard to maintain. The automation guild at WixEngineering have reduced the amount of flaky tests by utilizing what we define as the “Test State Pattern”, where every test transitions between states according to its behavior.

We will talk about the motivation, implementation and discuss how everyone can achieve the same.

Following topics will be covered during the talk:

– How to choose testing strategy?
– What patterns better to use?
– Protractor Tips and Tricks!
– Quick workshop and examples.
– Support tests and keep calm.

This talk is a brief overview of how we deal with UI test architecture on our project. Complex backend, SPA as a frontend, 20+ different brands and 100+ features for each, more and more code.

We will discuss:

– fakes and test doubles, approaches how to build and maintain them;
– development patterns, which help you to make your architecture more simple, stable and readable;
– tips and tricks – how to make your life with UI tests easier.

This talk will explain you that automation of API is not a challenge and everyone even with basic knowledge of programming language can create his own automated regression list using Postman.

We will review what is API and how to test it in general. Also we will learn how to make a Postman’s collection of tests and how to work with an environment variables. You will see how to run an automated API tests from Postman and from a command line.

If you do not know what is API and how to test it, but you want to do it and you are on your way to testing API, then this talk is just for you.

Not all desired capabilities where born equal:

– Some were born in the world of open source, while others were born as vendor proprietary properties.
– Some are mandatory, and some are optional.
– Some are clear and deterministic, others are vague and require reading and experimentation.
– Some make it easy to change vendors without breaking a sweat, while some will lock you into a specific implementation.

In this talk, I’ll explore the tradeoffs that a tester can make, and also explain the vendor point of view of the wild wild west of Selenium capabilities.

Test automation (TA) activity has become a key critical work to guarantee the quality of system under test (SUT) by driving test and also development effort effectively. To bring this efficiency to projects, companies are investing on TA projects in a more motivated way. The question here is how we should design the automation strategy to handle complex TA projects together effectively. It can be done by automating test scenarios as E2E (end to end). Vertical E2E TA consists of; automating Test Data Preparation Phase and Unit, Integration and UI tests. For horizontal E2E TA; UI and Integration test cases, which are automated, designed as integrated real user scenarios. I will tell about the prerequisites, principles and key factors to have E2E automated tests. And also I will share hands on experienced E2E test automation projects that Selenium was the key tool.

Many of you are doing THIS or suppose that doing. But at the testing conferences and meet-ups THIS is not acceptable. If this topic rises up, it is discussed quietly and almost in a whisper. There are people who decided to be in the opposition of THIS. But I was doing THIS openly for the last year and finally decided to share my experience.

This talk is focused on the method of White box testing. We will try to figure out what it is, how it works and why now it’s the best time to discard your prejudices and start using it.

I will talk about those parts of code where the most part of the bugs hidden, and why this method is one of the best ways of microservice testing.

Docker is a new and exciting virtualization technology, that allows individuals to get some great, easily scriptable and repeatable results. It’s especially exciting for development work flow, since it allows the developers and testers to have a lot of control over their environment without a hassle. However, since it is a new technology, this talk will talk about positive and negative sections of the new technology when applied to software development workflow.