52% of U.S. consumers said they would switch from a brand they like to another for better product quality.

Since many companies were forced to take a digital-first approach during the pandemic, digital customer experience has become paramount.

However, existing test automation approaches tend to take the focus away from the customer, requiring high investment in implementation and maintenance.

In this session, Fernando will make the case for why you should consider including low-code, E2E testing into your quality strategy, and share tips on which customer journeys to prioritize, how to integrate E2E tests into your pipeline, and what data to monitor to help you optimize quality for your users.

Are you tired of chasing your development team for object IDs, and having to update your test automation scripts every time the structure of your app changes?

In this session, we’ll give you an overview of how you can take a visual approach to mobile test automation.

We’ll explore different options for automating the UI of mobile apps without having to rely on its internals (for example, through OCR or image recognition).

Plus, we’ll use real-life examples to demonstrate how you can use this approach to use a single script to automate your app across devices and platforms.

How to add Playwright(Python) tests into an established repository of tests in other frameworks.

We started with a set of Gherkin tests in Feature files, with step definitions which are written in Ruby and Selenium for automating the browser.

Then, we added in Karate, which also uses Feature files, into the mix. Now, I'm adding in Playwright(Python) using the Behave framework so that these tests can be written in Feature files, too, but with the step definitions written in Python.

All the tests are in Feature files and every scenario is tagged with the type of test (@ruby, @karate, @python), which lets us ensure that the right test runner is used for each test. Py4J lets the Python tests run Java code, including some custom Java code which we wrote for our Karate tests.

Takeaways:
- If all your tests are in .feature files, you can use multiple frameworks together and continue to run your old tests alongside your new ones.
- Py4J lets Python tests run Java code, so you can make use of all the Java libraries as well as the Python libraries
- Java can run Ruby, so I can enable my new Python tests to run old Ruby code, written for our legacy tests, by using Java
- A "dry run" of all the tests matching a set of tags will yield JSON logs which contain all the tags of all the tests you want to run, which lets you make a list of all those tests and then divide the list according to type and run each list of tests with the appropriate test runner.

The golden rule of web performance states that for most web pages, less than 10–20% of the end user response time is spent getting the HTML document from the web server to the browser while 80-90% of the end user response time is spent on the frontend.

When we talk about performance testing, the most common activity that we do is to load test our backend servers. We come to a realisation that once we have optimised our servers and databases, that our application is now performant. However, this should not be the case.

Just because our servers have returned the response to a specific request doesn't mean that our users can see the response on the web page yet. There are many factors affecting frontend performance as well and it's as equally important to test to make sure that our users have the best user experience.

Historically, when we think of frontend and backend performance, we have to use separate tools. But what if there is one tool that can do this both?

In this talk, I want to introduce you to xk6-browser. xk6-browser is an extension to k6 which brings browser automation and end-to-end web testing to k6 while supporting core k6 features. It adds browser-level scripting APIs to interact with real browsers and collect frontend metrics as part of your k6 tests. With xk6-browser, this gives you the ability to measure how your frontend is behaving during certain events which would be difficult to catch from the protocol-level.

Here are a few takeaways for my talk:
- Learn why frontend performance is as important as backend performance
- Understand why performance testing is not just about load testing
- Know what xk6-browser is and why k6 has decided to introduce browser automation as part of the k6 ecosystem
- Know how to create a script using xk6-browser and combine it with existing features from k6

Creating great tests is only a start, the main job of the tests is to continuously give feedback during the SDLC process.

In this session, we will explore various ways to configure GitHub pipelines to orchestrate a pipeline including:

-- How to run E2E tests only after other tests are passing.
-- How to parallelize jobs for reducing execution time.
-- How to retry failed tests.
-- How to run a specific job at a specific time, say nightly.
-- Collecting test results and show them on the PR.
-- Create and collect code coverage metrics and display them on the PR.
-- Visibly show build and test states as badges on top of a PR.

In this session, you'll learn about:

-- What are the challenges in regulated markets (MedTech, Pharma, ...) in case of 3rd party software
-- What problems are regulated customers facing because of DevOps
-- Why Test Automation is a path forward for customers in these markets
-- How to address the typical challenges in regulated markets: 100% Traceability, Zero-Level-Of-Intrusion, mandatory audits

In the frantic race to automate everything, one critical fact often gets overlooked… that test automation is NOT testing.

Many organizations equate a comprehensive automated test suite with an effective software testing function.

However, their definition of test automation is often limited to the automated execution of scripted test steps.

Even in the best-case scenario, this approach can give a false sense of security - especially when executing automated checks is the only “testing” that’s performed in the development cycle.

In this session, Lee will discuss why he sees the craft of software testing being swallowed up by test automation.

He will help you think beyond just the execution of scripted tests and apply automation principles more generally to testing activities.

You will learn how to look at testing and automation as complementary activities and take back techniques for using a context-driven approach to automation to improve both the effectiveness and efficiency of your software testing.

80% of ERP transformations go over time or budget. While most transformational leaders recognize that utilizing DevOps can streamline these cumbersome projects, actually incorporating DevOps into ERP transformations has proven to be quite the challenge.

In this session, Pankaj Goel, CEO of Opkey, will explain how test automation is key for incorporating DevOps into ERP transformations, and will share how he used DevOps methods to successfully migrate 40 of The GAP’s business units from Oracle EBS to Oracle Cloud.

Are you tired of chasing your development team for object IDs, and having to update your test automation scripts every time the structure of your app changes?

In this session, we’ll give you an overview of how you can take a visual approach to mobile test automation.

We’ll explore different options for automating the UI of mobile apps without having to rely on its internals (for example, through OCR or image recognition).

We’ll use real-life examples to demonstrate how you can use this approach to use a single script to automate your app across devices and platforms.

This talk will cover the basic concepts of Automation, Robotics Automation, intelligent automation, etc.

Audiences will be well equipped with the knowledge of the industry jargon for automation. And also be aware of how to kick-start their automation journey.

This talk will also be comparing automation technologies with one another and also be covering the common myths that exist alongside them.

The key takeaways will be :

1. Audience will be well equipped with Robotics and intelligent automation concepts and how to kick start their personal/professional journey in it.
2. Audience will be aware of the common use cases across various industries that leverage the automation and intelligent automation strategy.

Since ancient times we have heard the phrase "you do not ever test in production." That phrase, at a point, was reasonably accurate for all QA endeavors, especially for performance testing.

This taboo came partly from the misconception that performance testing meant loading and determining the system's limits by bringing it down with load tests.
But that was the past.

We are now in the modern age of CI/CD, service-oriented applications, the ever-expandable cloud, spread applications with microservices, and much more.

Performance testing is also evolving with these modern changes, just trying to push the system to its limits is challenging, weird, and at times pointless.

In this talk, Leandro will flip the establishment. He will explain why the traditional methods may not be so suitable anymore.

And in the talk, you will find several recommendations to embrace these types of tests in your precious production environments.

The recommendations will be as mind-blowing as load testing in production and even reaching the realms of manual load tests—staggering and eye-popping information delivered as usual with fun analogies and fantastic stories.

Attendees will learn about Cypress techniques and plugins that will allow them to incorporate security, performance, visual, and accessibility tests to their existing API and UI test suite.

We'll also talk a bit about how much testing is enough and how to organize tests.

In the recent years, Agile has become a household name in the Development and Testing organization alike. While many teams adapted Agile practices like Daily Scrum, shorter Sprints and Retrospectives, they are still struggling due to manual build and deploy processes, slow and insufficient testing and integration issues. One needs to realize, that Agile cannot truly function without DevOps and DevOps without Agile.
This session will cover 10 steps that will help any company to get on the path of Continuous Integration and move closer towards the coveted Continuous Delivery. These will include setting up Repository for common artifacts, understanding and documenting the Build, Test, Deploy process flow, setting up of Continuous Integration, Automation, Monitoring and Reporting.
While adopting DevOps and following these steps does not guarantee smooth releases 10 times a day, it definitely puts the company on the right track towards faster releases with higher quality and happier employees.

How to combine open source tools to build powerful test automation capabilities.

Design a Test automation framework that maximizes output while essentially freezing the lines of automation code to maintain.

-- How to break down an application into functional areas
-- How to create reusable steps that work for any scenario
-- How to create an object-oriented framework

In 1981, Judas Priest released Point of Entry. Oft maligned, this album contains the killer tune Solar Angels. Coincidentally, some of the lyrics from Solar Angels, “Diamond visions softly breathing fire”, come to mind when thinking about assertions.

When automating, we often need to check “composite” constructs, i.e. those constructs whose subparts we want to treat as one amalgamated “pass” or “fail”.

One example of this is the response received from a REST GET call; another example is a grid of data that on a GUI or web page.

If we hard assert on each field or grid cell, we get one failure at a time, which is not always efficient, especially for tests that take “a while” to run; if we address one failure, we have to run again to uncover the next failure.

Additionally, a group of failures may be more indicative of the actual problem than one problem in isolation.

Enter the “soft assert”. A soft assert is a way to amalgamate checking multiple pieces of data into a single pass/fail.

Join our speaker to hear when and how to use soft asserts, as well as when and how to NOT use soft asserts.

We’ll also see a live demo of creating a soft assert object if your programming language doesn't support one or you need a special-purpose one.

Adoption of "0 tolerance to failures" automation approach in cross-functional Agile team.

-- Why do you want to adopt " 0 tolerance to failures" test automation strategy: pros and cons
-- Defining strategy, goals and team commitments
-- Path to success: management support, iterative process, time commitment, teamwork
-- Lessons learned: changing mindsets, just-in-time innovation, and good "side effects"

Imagine having an application under test where documentation is sparse, people with information can’t
be reached, or you’re otherwise left to ask yourself ‘but how does it actually work’?

In this Masterclass you will overcome all these worries and find solutions to explore your application, create targeted API tests and automate them. So at the end of this hands-on Masterclass every participant has made their own automated API-test.

To accomplish this we first start to explore a GUI that is connected to the API. Because we believe that
learning should always be fun, the GUI isn't just a boring webform, it's a digital escape room!

At the start of the workshop the participants will explore the GUI by trying to escape from the escape room. After that it’s time for the real work. Search for the API requests made by the application and automate them.

During this Masterclass we will support each participant on their own level. As a result the class is
suitable for testers with beginner or intermediate level experience with API testing and/or test-automation who wish to improve these skills.

Key Takeaways:
- Use DevTools to map the API
- Ways to map and process the information gained from the API
- Tactics, tips & tricks to focus on the most useful and important API calls first

Run Security Test via Selenium Automation Suite.

Security Testing is always done manually and there is a security team who does it.

Now it's time for our QA's to upfront run the security test via our regular regression suite to find any urgent or high-priority leakages. This helps in a quicker release process rather than waiting for the results from the security team.

APIs are one of the limelight topics in recent years, everywhere we can hear this term. Even though APIs (Application Programming Interfaces) have existed ever since software existed, in recent years it has become a critical requirement for being able to scale and grow your Product.

APIs allow pieces of code to bridge together as applications so they can work cohesively together.

API Testing has reached stardom nowadays. This process helps to ensure that performance, functionality, security, and reliability of software meet expectations - in other words, that the server (API) is able to serve several visitors simultaneously, return to the client, bring the exact response that was hit on the browser and so on.

If this testing wasn’t performed then consequently, ineffective APIs can result in integration difficulties, poor software quality, user frustration, and revenue losses.

POSTMAN is an API development environment used by more than 7 million developers today. With POSTMAN you can design, mock, debug, test, document, monitor and publish APIs all at the same time. Postman is very convenient when it comes to executing APIs. Postman is preferred due to its handy and simplified features.

Many would be familiar with POSTMAN testing essentials, but in recent times POSTMAN team has introduced a new codeless feature “Flows”, which is an API workflow builder.

These days Codeless testing is more popular where the tester never has to write a single line of code, in similar lines "Flows" will help you to automate your API requests without any coding. Flows is basically a codeless approach to chaining processes together. It really opens up Postman to a whole new audience.

So what will we uncover in this session?
- Glimpse of Low-Code / No-Code
- Know about Flows and its concepts
- Traditional API Test Automation approach
- Benefits of using Flows
- Interesting Use Cases in FLOWS

During the session you will learn about Report Portal - what kind of features it has and how they can help with automation analysis of failed tests. Some lessons which we have learned the hard way. And last but not least some statistics before / after Report Portal integration in our company.

Learn to design test cases for solid automation.

We have tons of tutorials on how to use Selenium, Cypress, and Playwright but it is hard to find tutorials or talks which will help an exploratory tester design a test case that is more suitable for automation.

During my 15+ years of career, I often work with people who are early in their automation career but they lack the concept of how to design a good automation test case.

For example, how to use the before and after tests effectively to make sure a test is not fragile. In this talk, we will go through some real-life examples of how to adopt design thinking and what you need to know if you are taking your first step toward automation testing.

An introduction and examples on how to do test automation with Winium and AutoIt.