Archive for December, 2016

Report Portal – open-sourced tool for test automation reporting by EPAM. Build by test automation engineers. Every project spends time to build own reporting, it’s especially indispensable for test automation in distributed systems, for test automation with large number of test cases, the same as for a small teams.

Report Portal gives it out of the box. Full-featured reporting management tool with custom dashboards, widgets, metrics, customizable defect type, history and smart analysis based on Machine Learning.

It can give you not only one place for all your test automation results, but also reduce the effort of the team for result analysis. From this talk you will get not only introduction but also features review, tech specifics, comparison with competitors, benefits and advantages, how it could work for you and your project. And it’s free, it’s open sourced.

As Selenium WebDriver is known to be a tool for browser automation and not for testing, we are doomed to use some testing frameworks to get efficient at automating web tests. But should every project reinvent the wheel? My answer is – “no!”.

Selenide (http://selenide.org) is a well-known matured (5 years old) web test automation framework with a large community, which has already solved almost every typical web automation problem. Just write your web tests in concise, easy to read manner, and concentrate on your business problems and not on taming your browsers.

In this workshop you will learn how to configure and start using Selenide from scratch in your project. While learning basics, we will be solving typical web automation tasks with real application exactly the way you would be doing it on your job!

Attendee should have basic understanding of Java, and how to write automated web test in general.

BDD stands as Behaviour Driven Development and was invented to increase efficiency of ATDD by involving Business Analysts/Product Owners to write Acceptance Criteria in “ready to be automated by developers” format – Gherkin. Then customers and managers invented Bullshit Driven Development when had made automation engineers write both Gherkin and implementation of its steps just for one reason: make tests and their reports readable. This is a classic “hammering nails with a microscope” example, when engineers have to add additional limiting layers to test framework for no any valuable reason. Because… There is much simpler and more powerful way to make simple xUnit tests and reports readable. And in this talk we will learn how. How to implement common xUnit tests in BDD style and make everyone happy – test automation engineer, customer and manager. 😉

Software Developer in Test is relatively a new role in IT. Industry got more used to the titles like QA, Test Automation Engineer, Developer… Still this kind of roles distribution shows poor effectiveness and brings such things like huge suites of end to end tests as a quality gate. If you want to implement test pyramid, you should consider of such a role in your team.

What skills should have this person? What challenges and daily problems does he/she face? Can he/she change production code? This talk is about all these and many others connected questions. Perhaps, after this talk you will reconsider daily quality assuring approach.

Are your tests objectively bad? Do your tests fail for no good reason? Do you get qualitative analysis of your test suite after every run? Join Marcus Merrell as he presents a new test analytics service developed with Selenium guru Dave Haeffner. This service attaches itself to your test framework, and passively sends data and analytics about your tests’ behavior to a web service. Once your tests have finished their run, a report gives you an overall assessment of the stability, reusability, and overall health: it gives you a grade.

This talk will step through the core tenets of good test and page object design, locators, and a repeatable and quantitative approach for assessing your test code. When you’re done, you’ll be able to see how your tests and page objects stack up, and what changes are needed to help them stand the test of time.

This talk was composed with the permission and cooperation of Dave Haeffner.

This is all about making the testing process and outputs visible to the project team and to the company as a whole. We’ll try to answer questions below to make sense of our outputs and give meaningful metrics to our stakeholders:

– Why do you need to display test metrics in a project?
– What do you need to display?
– How do you display them?
– Some common mistakes to avoid on your information radars.

In this master-class we will review popular Page Object design pattern:

– what is motivation behind it?
– how to split application under test in Page Objects?
– how to simplify tests and increase code reuse with good implementation of Page Objects?
– how technically Page Object implementation works with PageFactory for elements initialization?
– when this pattern doesn’t work well?
– what frameworks and libraries could help with Page Objects creation?

All this questions will be answered during live coding sessions on realistic examples. Target audience is beginners and middle level, but some parts could look interesting even for experienced test automation engineers.

Working in many companies as consultant, delivery manager or tech lead I have always seen the same mistakes made in test automation process. I could count successful cases on fingers of one hand. Sometimes people don’t understand the true value of test automation, sometimes just could not organize this process spending lots of money and time without any significant result. I want to share 5 top mistakes aggregated from whole my practice and solutions I recommend for them.

How to stop writing code and start writing automated tests. Based on real story.

(Example of how to create simple, readable and powerful REST API test automation solution with Spock and Groovy)

This talk is about how to test integrations in advertising project with multiple NoSql solutions, billions ads every day in real-time, many relations with external projects, doing it continuously and really quickly.

When we talk about mobile testing on real devices, it’s important to protect yourself against the challenges we may face during the environment maintenance.

Are you still wondering about how to automate the lookup process on real devices? Still struggling with manual Appium nodes configuration? And what about the tests’ scaling? Do you really think that sequential execution would be an option? But how to allocate the tests between real devices? And how to create platform-dependent pools?

This talk will help you get answers to all of these questions.

If you are using Selenium as your test automation solution and you are testing web applications; there is a good chance that your company also has at least one mobile application. The common sense tells us that Selenium cannot be used for native apps for mobile, but with the times changing you’re probably asking yourself if you can at least use your Selenium skills with mobile test automation as well; the answer is a big “yes”.

Beyond any doubt, whether you establish a solid mobile test automation framework yourself or someone does it for you, it will bring many benefits. Some of the most critical ones include: a powerful foundation to cope with the mobile testing challenges and a systematic approach to shorten the time-to-market delivery by supporting the quality of your mobile products in preliminary stages.

My session mainly focuses on the challenges of mobile test automation (device variety, platform/OS diversity, operator/carrier issues, choice of native vs. HTML 5, emulator vs. real device testing and etc.) and it will guide attendees to practically utilise the solutions as Appium & Selendroid based on their experience on Selenium.

In this talk you will get ideas about how you can instrument test result information to provide actionable data, paving the way for more robust, reliable and timely test results.

By capturing this information over time, and when combined with visualization tools, we can answer different questions than with existing solutions (Allure/CI tool build history). Some examples of these are:

– Which tests are consistently flaky.
– What are the common causes of failure across tests.
– Which tests consistently take a long time to run.
– Using this information we can move away from the ‘re-run’ culture and better support continuous integration goals of having quick, reliable, deterministic tests.

This talk is about ways how use SoapUI tool for:

– Test Design.
– System testing and Integration testing.
– Test cases management.
– Continuous Integration.

All practices will be described with focus on REST services testing.

Responsive web design has become the preferred approach for building sites and apps that provide an optimal viewing and interaction experience on any phone, tablet, desktop or wearable device. However, automatically testing these responsive sites and apps can be quite a challenge, due to the need to cover all supported layouts, their respective navigation, and visible content.

In this session we will implement a complete Selenium-based automated test for a popular responsive website from scratch. You will learn how to effectively design responsive page objects, implement generic tests that work for all the layouts of your app, control the browser’s viewport size in order to accurately target layout transition points, incorporate layout-specific assertions in your tests, and visually validate the correctness of your app’s layout​. We will also share tips and best practices for test planning and execution.

White is a framework for automating rich client applications based on Win32, WinForms, WPF, Silverlight. It is a free, open-source framework, which can provide competition for commercial test automation tools for Windows. Also, it is great to use this framework with WebDriver for creation integration test on huge software solution which contain web and desktop parts.