SauceCon Online 2021
April 20 - 22

What’s Next For Testing?

Abstract
Agile and DevOps have created the big illusion that testers are no longer needed and that developers are taking full-time control of testing. But while some enterprises have indeed succeeded in getting developers more involved in testing, there are still hundreds of thousands of manual testers working every day to test applications and ensure digital quality.

In this keynote address, Diego Lo Giudice, VP and Principal Analyst at Forrester Research, will examine how AI and ML are making it possible for non-dev testers to increase automation and test smarter than ever. Diego will specifically explore:

• The latest and most impactful trends in software testing
• Why testing is better when it involves business, technical, and developers testers
• The role of AL and ML (and even Bots!) in the future of testing

Bio
With Forrester since July 2005, Diego primarily contributes to and advises on Forrester’s offerings for Application Development & Delivery Professionals. He partners with Forrester’s global application leaders and is a leading expert on SDLC processes and practices, covering topics such as Agile development, Agile and Lean transformations, Agile development sourcing strategies and services, Agile testing practices and tools, DevOps, and software testing and quality, with a key focus on systems of engagement. Diego also covers software delivery metrics, artificial intelligence, and open source governance.

His 28 years of industry experience, in addition to application development, allow him to give expert advice on change management programs for optimizing the overall modern application delivery process, execute technology management assessments, review technology management strategies, and make comparisons. He also has experience in complex mission-critical projects and client engagement management.

The Truth About Agile

Abstract
Chances are, if you’ve been in the software development industry for any amount of time, you’ve heard the word “Agile” thrown around a time or two. Perhaps you’ve been part of an “Agile Transformation” or you have attended a certification course for Scrum or Kanban. In the 20 years since the Manifesto for Agile Software Development was drafted, “Agile” has taken on a life of its own. But what is “Agile” really, and what does it mean for you? Is it story points and two week deadlines? Is it kumbaya and “soft skills”? In this talk, we’ll get into some real truths and real talk about what it means to be agile in today’s changing world.

Key Takeaways:

• The origins of the agile movement
• Agile vs. agile – is there a difference?
• The Truth about Agile and business agility.

Bio
Melissa Boggs is a leadership, agility, and culture coach and executive with background in leadership, business, and product development. A Certified Enterprise Coach with an MBA, she blends education, experience, and enthusiasm to work closely with leaders on their most challenging business problems. She is a former nonprofit executive and board member, having served on the Board of Directors for both Scrum Alliance and Agile Denver. In 2020, she was privileged to present at the World Business and Executive Coach Summit, and has been featured in Business Coaching and Authority magazines. She is currently serving as the Vice President of Business Agility at Sauce Labs.

Dopamine Driven Development

Abstract
Software development can be a real grind, but one thing that makes it more bearable is the joy of a passing build. Not only is that green bar important when you’re iterating on a feature, but it’s normally a vital part of determining whether or not your software can be released. Getting to a green build as quickly as possible allows you to experience that joy of a passing build more frequently, and allows you to verify that the next release is good more quickly than your competitors. It’s a vital building block as we move towards Continuous Deployment.

Given how important fast builds are in your software development, how can you make the most of Selenium 4 to help get you there? In this talk, we’ll cover some of the new features in Selenium 4 that we added to make your life easier and your builds faster, and we’ll explore how you can best use Selenium to help reduce your build times.

Bio
Simon Stewart is the creator of WebDriver, the open source web application testing tool, as well as a core Selenium developer. WebDriver remains a hot topic as it is currently going through a W3C (World Wide Web Consortium) specification process, which Simon is a co-editor of.

He describes himself as “undeniably hairy”, and holds a BSc in computer science from Nottingham University.

The Future of Technology

Abstract
The world of technology is changing right before our eyes. Development teams are moving at speeds that once seemed unimaginable and delivering new products and capabilities that we never thought possible.

In this keynote interview, Aled Miles, president and CEO of Sauce Labs, is joined by Toby Redshaw, former SVP of enterprise innovation and 5G solutions at Verizon, to discuss how organizations can harness the power of modern technology to create sustainable growth and improve customer relationships.

A leading authority on business transformation, Redshaw will discuss how to balance innovation with pragmatism, drive competitive advantage through real-world IT strategies, and the role of testing and development in building digitally confident companies and customers.

Bio
Toby Redshaw left Verizon after four and half great years in early April. He was responsible for Verizon’s Enterprise Innovation and 5G Solutions area. He previously ran 5G Ecosystems, Innovation and Product Development, plus the AR/VR and Location Services/Geo Intelligence (AI) Businesses.

Prior to joining Verizon, Toby was most recently CEO of Kevington Advisors, a leading-edge consultancy offering services in enterprise tech intensive strategy and transformation, coaching start-ups and various government/military engagements. He was a co-author this year of a book published by Special Operations Command and Lawrence Livermore National Laboratory on emerging technology and Special Operations.

Toby previously held Global CIO positions at American Express and Aviva PLC, HQ in London. His responsibilities also included Risk, NPI, eCommerce.

He had simultaneous product, CPO, marketing, strategy, venture, diversity and technology responsibilities during the six years prior at Motorola, while also working as Executive Chairman of a start-up portfolio company.

Toby also helped found and run a global start-up, one of the first cloud-based solution platforms in 2000 and next gen supply chain for hospitality out of Silicon Valley, China, London, Memphis and Ohio. He has served on numerous boards and advisory boards.

He started his career as one of the first employees on the international side of FedEx, where he had a 17-year career in business and IT based in Asia, Latin America and US.

Among his recognitions, Toby was named to Top CTO 25 – Most Influential IT leaders by InfoWorld and Top 50 Global CIOs by InformationWeek.

Toby is the founding chairman (emeritus) of the Kellogg Innovation Network (originally at Kellogg Graduate School of Business, now TWIN Global). He co-chaired the working group on scale disruptive technologies at the Council on Competitiveness (2020), sits on the DELL IT Advisory Board, the advisory board of the Lake Nona Impact Forum. He currently mentors/advises several start ups. He was born and raised in Mexico City and is proud to have become a U.S. citizen in 2014.

Maintaining and Upgrading Custom Test Frameworks

Abstract
Stability and reliability of test frameworks are integral to the trust and quality of test automation. More often than not, we are faced with breaking upgrades or unforseen regressions. In this talk, Abhigna Srinivas will share learnings from her experience maintaining and upgrading custom test frameworks. She will touch on patterns that have helped the Netflix team ensure stability while improving scalability.

Key Takeaways

• Tips for testing a test framework
• Backward compatibility – benefits and use cases
• Premerge pipelines for test frameworks

Bio
Abhigna Srinivas is a Senior Software Engineer in the Website tooling and delivery team at Netflix. She has over a decade of experience in building tools and frameworks in various technologies for large enterprises. She is particularly passionate about architecture and design principles that drive scalable and maintainable software.

Adding More Security to Your Testing and Automating

Abstract
Security testing is a highly technical set of skills, covering a wide domain of knowledge that can take a long time to learn and gain proficiency. We already have enough to learn with software testing and even more when we add in automating. So are there any simple ways to increase the scope of what we already do, that provide more insight into the security of our application? Answer: Yes. And in this talk we will cover practical steps, dos and don’ts to add some security focus fast, without spending years learning how to hack applications.

Key Takeaways

• Security Do’s, Don’ts and Risks that we need to consider for our test process
• How to add additional tooling around our existing testing and automating
• Proactive steps to improve security that are easier to adopt than learning to Hack

Bio
Alan Richardson has more than twenty years of professional IT experience, working as a programmer and at every level of the testing hierarchy from tester through head of testing. Author of the books “Selenium Simplified” and “Java For Testers”. Alan also has created online training courses to help people learn Technical Web Testing and Selenium WebDriver with Java. He works as an independent consultant, helping companies improve their use of automation, agile, and exploratory technical testing. Alan posts his writing and training videos on SeleniumSimplified.com, EvilTester.com, JavaForTesters.com, and CompendiumDev.co.uk.

The Future of Technology

Abstract
The world of technology is changing right before our eyes. Development teams are moving at speeds that once seemed unimaginable and delivering new products and capabilities that we never thought possible.

In this keynote interview, Aled Miles, president and CEO of Sauce Labs, is joined by Toby Redshaw, former SVP of enterprise innovation and 5G solutions at Verizon, to discuss how organizations can harness the power of modern technology to create sustainable growth and improve customer relationships.

A leading authority on business transformation, Redshaw will discuss how to balance innovation with pragmatism, drive competitive advantage through real-world IT strategies, and the role of testing and development in building digitally confident companies and customers.

Bio
Aled Miles is a British-American information technology executive and internet security expert based in San Francisco, CA. He currently serves as CEO of Sauce Labs, and was previously CEO and member of the board of global tech firm TeleSign Corporation. He is a graduate of St. Mary’s University and the Stanford Graduate School of Business, and previously served on the executive committee as a Senior Vice President at the global security firm, Symantec.

Managing the Test Data Nightmare

Abstract
Test data for automated tests can be a nightmare to manage. Data must be prepped in advance, loaded before testing, and cleaned up afterwards. Sometimes, teams don’t have much control over the data in their systems under test—it’s just dropped in, and it can change arbitrarily. Hard-coding values into tests that reference system tests can make the tests brittle, especially when running tests in different environments.

In this talk, I’ll teach strategies for managing each type of test data: test case variations, test control inputs, config metadata, and product state. We will cover how to “discover” test data instead of hard-coding it, how to pass inputs into automation (including secrets like passwords), and how to manage data in the system. After this talk, you will wake up from the nightmare and handle test data cleanly and efficiently like a pro!

Bio
Andy Knight is the “Automation Panda”—an engineer, consultant, and international speaker who builds solutions for software testing problems. He has designed and built robust test automation projects for operating systems, service APIs, and Web apps with thousands of tests running continuously. He is also the lead developer for Boa Constrictor, the .NET Screenplay Pattern. Read his tech blog at AutomationPanda.com, and follow him on Twitter at @AutomationPanda.

Test Driving Selenium 4

Abstract
The Selenium WebDriver maintainers have been hard at work on a brand new version: Selenium 4! Some of the features are already available in beta mode, which allows us the opportunity to try it out, provide feedback, and even pitch in with development.

Together, let’s explore some of the most promising new features of Selenium 4. Angie Jones will lead the discussion as we test drive new features such as Relative Locators, Chrome Devtools Protocol (CDP), and more.

Code samples will be provided. Let’s take Selenium 4 for a test drive!

Key takeaways:

• Deep dive technical look into Selenium 4 features
• Best practices and caveats for using these features
• Awareness of new possibilities within our tests

Bio
Angie Jones is a Senior Developer Advocate who specializes in test automation strategies and techniques. She shares her wealth of knowledge by speaking at software conferences all over the world, teaching courses, and writing tutorials on angiejones.tech. Angie is known for her innovative and out-of-the-box thinking style which has resulted in more than 25 patented inventions in the US and China.

Test Automation Beyond Java 8

Abstract
While most people are still using Java 8 from six years ago, new versions of the language are being released every six months! The latest versions provide an abundance of new features such as functional programming capabilities, switch expressions, local variable type inference, additions to the Stream API, new factory methods for Collections, text blocks and much more.

With so much content, your Java upgrade should be more than simply the update of a jar file. Your test code no longer has to be as verbose as it once was, meaning less code to write and maintain!

This talk will introduce the new features of Java 9 – 14 and provide examples of how these features can be used for test automation.

Key Takeaways

• Introduction of new features in the latest 6 releases of Java (9 – 14)
• Examples of how the features can be used for test automation projects
• Greater command of the programming language

Bio
Angie Jones is a Senior Developer Advocate who specializes in test automation strategies and techniques. She shares her wealth of knowledge by speaking at software conferences all over the world, teaching courses, and writing tutorials on angiejones.tech. Angie is known for her innovative and out-of-the-box thinking style which has resulted in more than 25 patented inventions in the US and China.

Self-healing E2E Tests with Healenium

Abstract
Do you want to spend less time on test maintenance and overcome the instability problems of end-to-end automated tests? With its self-healing capabilities, Healenium is an invaluable solution to overcome these challenges.

During the session, EPAM Quality Architect Anna Chernyshova will show how, with a few updates to your Selenium script, you can adapt tests to deal with UI changes and fix issues with broken locators automatically.

Key Takeaways

• Understand the self-healing capabilities of Healenium
• Learn how to use Healenium with your existing Selenium scripts
• Learn how to run and analyse self-healing E2E automated tests

Bio
Anna Chernyshova is a Quality Architect at Epam Systems with progressive experience in automated testing and project coordination. She has strong experience in test automation tooling and how to start, drive, and complete QA projects. Anna is an adherent of engineering and DevOps practices, and a driver of Healenium development.

How to Shift Left and Right Effectively with AI

Abstract
AI is a big promise, a buzz word that has earned a lot of skepticism – some of it justified.

In the presentation, Aviram Shotten will present the thought process and outcomes of powerful AI use-cases in testing. He’ll discuss how we can make the life of Quality professionals better, and subsequently produce and release better software, quicker.

Bio
With 15+ years of experience in Quality Engineering around the world and as Chief Solutions Engineering in Qualitest, Aviram is running a team which is all about innovation, customer centricity and technology. From AI to Cyber, Aviram is responsible to make sure that Qualitest’s customers are served with the best Quality Engineering solutions globally.

Transitioning Into QA: My Shift Left

Abstract
When looking to break into the technology industry, non-tech persons can be the secret weapon for a tech company because we bring different perspectives to the team which can have a positive impact on the product.

In this talk, Brittany Stewart will present her journey from Business to Technology and share how she used serendipitous skills to help her advance in the QA role. She has learned many lessons and gathered unlimited ideas from her experiences. Through this presentation, she will share how those experiences from different spheres of the business world can be applied to technology.

Key Takeaways:

• Transferable skills that help in a Quality Assurance role
• How to apply non-technical skills in a Quality Assurance role

Bio
Brittany Stewart is a Software QA Consultant based in Jamaica, where she works with a leading tech innovation company. She has worked in a variety of capacities over the last five years and has made the transitional journey from business to the tech world by identifying ways to transfer her skills and build relationships that open doors to opportunities in technology.

[WORKSHOP] Crafting a Test Framework

Abstract
If you have ever maintained a Selenium test suite, you know that the most expensive piece is dealing with the maintenance costs, not the creation or execution costs. There are straightforward ways to leverage your framework to minimize flakiness and make it easier to update your test code only when needed. We’ll walk through testing a sample real-world application focusing on how each of the components work together.

Outline/Structure

• Writing good tests
• Using Test Data
• Working with Page Objects
• Managing Synchronization
• Encapsulating Objects
• Executing Tests at Scale

Key Takeaways

• What to prioritize when developing test tooling
• How different framework components work together

Bio
Chris is a test automation expert whose career is focused on all aspects of test automation. He has a passion to share his knowledge and what he has learned over the years. As a new Saucer, he currently focuses on helping external teams succeed with all things test automation.

[WORKSHOP] The Nuts and Bolts of WebdriverIO

Abstract
While you can build a custom framework that fits your needs there are often already sophisticated setups or frameworks available that get you up and running very quickly.

WebdriverIO is one of these frameworks that is written in Node.js. It gets you up and running within minutes and allows you to scale up your test suite while maintaining your execution time by running tests in parallel. With its huge project community it is an ideal choice for small as well as big projects that use modern frameworks such as React, Angular or Vue.js.

In this workshop you will learn everything you need to know to run a successful, stable and maintainable WebdriverIO framework. It starts with an introduction to the project and the basic concepts and will end with a sophisticated framework that includes testing strategies like Frontend Performance Testing as well as complex browser interaction with Puppeteer.

Outline

• Introduction
• Setup Environment
• Writing an automation script using Standalone Mode
• WDIO Testrunner
• Use of Reporter and Services
• Page Objects
• Performance Testing
• Go Pro

Learning Outcome
This course will not only teach you the basic knowledge of browser automation but also provides a hand-on-experience that you can take back to your workplace and directly apply it to your projects.

Bio
Christian Bromann is a member of the Open Source Program Office at Sauce Labs and is working on various open source projects related to test automation and Node.js. He represents the company as Advisory Committee representative at the W3C and the WebdriverIO project as core contributor in the OpenJS Foundation Cross-Project Council. In the past he has been leading various product initiatives at Sauce Labs including extended debugging capabilities for automated tests as well as frontend performance testing using WebDriver.

[WORKSHOP] Run Your Tests Anywhere

Abstract
Do you have a few JavaScript or Java tests and you need your colleague to run them for you? Oh, they don’t have Node or Java installed? What to do? Docker is the solution!

Run your tests on your laptop, on your colleague’s laptop, run them on a local or a remote Continuous Integration server (CI). Combine Docker with your tests to avoid the dependency hell and enable anyone, anywhere to run them. Docker is commonly seen as a tool to package and deploy applications to different environments, but it is very useful in testing frontend and backend applications.

Putting your tests inside a Docker image can be daunting at the beginning, but a basic understanding of how Docker works, how to create Docker images and run Docker containers will enable us to run our tests anywhere.

This workshop will show you great foundations and concepts to run tests (and potentially any application) in Docker, which you will learn through practical exercises. We will go in detail through the process of putting a test suite in Docker, from creating the Docker image and running it locally to the point where we run our tests on a complete new CI. We will cover the common pitfalls when using Docker and best practices to build good Docker images and run stable Docker containers in different environments.

Outline

• Introduction and quick environment check
• Docker introduction
• Introduction to our testing application (to be used along the workshop)
• Putting the application in Docker and running it, as a practical exercise
• Writing a few tests to test our sample application and using Docker to run them inside a container
• Run multiple Docker containers via docker-compose to test our application in different environments
• Running tests in a continuous integration pipeline
• Wrap up

Learning Outcomes

• Get insights on how an application can be containerized to make testing easier
• Scale-up test suites by running them in parallel and in different environment combinations
• Orchestrate multiple Docker containers to simplify test setup and execution
• Integrate the different elements from the training to build test setups that fit better your web application testing needs
• Identify and put together all the moving pieces of the test setup to facilitate the configuration of a continuous integration pipeline

Bio
Diego Molina is a Software Engineer who is fascinated by testing. He is a Selenium core committer. He loves enabling testers and developers by creating helpful testing tools and infrastructure and through versatile workshops. Diego can often be spotted speaking at Selenium/Appium/Testing conferences and most of the time you can find him on the Slack channel for Selenium. Currently, he works at Sauce Labs as a Senior Software Engineer.

The Ins-and-Outs of E2E Tests – What Every Tester Should Know

Abstract
We have written in excess of 10,000 e2e tests for TestCafe Open Source and we’ve learned that regardless of the capabilities of a testing framework, successful tests are a function of how a tool is used.

In this presentation, we’ll share practical advice and e2e best practices that can be applied to any testing framework. You’ll learn how to organize tests, write selectors, and test advanced usage scenarios.

Bio
Don Wibier has been programming for more years than he can count. At the age of 15, he built a ticketing and reservation system in Clipper for his father’s cinema, for which he and his friend were compensated with a brand new 386 PC!

After studying electronics and IT, Don embarked on a career in development, working with some of the biggest companies in The Netherlands and developing multi-tier enterprise solutions. Seeing an exciting future with the internet, he started building Delphi-based ISAPI DLLs in combination with application servers and databases. Working with an internet startup, he architected one of the fastest online services for finding and booking airfares. Don then built one of the most user-friendly Content Management Systems available, which is even now powering hundreds of web and mobile implementations across the world.

As Technical Evangelist at DevExpress, Don is eager to share his knowledge and experience with you!

Integrating Axe Accessibility Tests into the Sauce Labs Dashboard

Abstract
According to the World Health Organization, one billion people in the world, or 15%, have a disability. The world’s largest minority is an addressable market that is often overlooked. Accessibility is the practice of making the web and apps accessible to everyone, including those with disabilities; however, many enterprises struggle to create, maintain, and scale their digital accessibility efforts.

In this talk, Dylan will demo how to use the axe-core rules library in Sauce Labs Dashboard to perform automated accessibility tests as a part of your existing testing process. He will also review agile testing team practices for accessibility.

Key Takeaways:

• What is accessibility and why should you be testing for it
• How to use the axe-core rules library in Sauce Labs Dashboard to perform automated accessibility tests as a part of your existing testing process.
• Agile testing team practices for accessibility

Bio
Dylan Barrell has been working in the accessibility field for over 10 years. As Chief Product Officer at Deque, he has had the privilege of advising Deque’s Fortune 500 customers on how to integrate accessibility into their development processes. He founded the axe family of accessibility testing products and leads Deque’s software development teams in pushing the boundaries of accessibility at scale.

Horrible Adventures through Code: Slack Plugin Edition

Abstract
A few months ago, I checked out the source for the Sauce Labs plug-in for Slack, intending to add Slack Workflow functionality, and…

Oh Dear.

The problem wasn’t outdated or messy code (although it could do with a refactor) – the problem was the tests. Disorganised, hand-mocked, outdated tests. Yuck.

So let’s fix it! We’ll use API Fortress to ensure we’re using the Sauce Labs REST API correctly, and refactor tests live to make them understandable, neat, and useful. Once we’re done, we’ll tackle part of the Express web-app that powers the plugin itself, relying on the Power of Tests to keep things functional and bug free.

Attendees can expect to take away an approach to understanding tests in an unknown code base, an understanding of how using API Fortress helps testing integrations, and some tips and tricks on refactoring test code for functionality and readability.

Key Takeaways:

• A suggested approach for understanding tests in an unknown codebase
• An understanding of how API Fortress can help test platform integrations
• Tips and Tricks on refactoring test code for functionality and readability

Bio
Dylan has worked for Sauce Labs for seven years, helping customers learn & solving problems. His passion is sharing knowledge and making people’s lives easier through technology, which he’s been doing for 14 years. He’s been involved in Evangelism, QE & Development, as well as Product Design and Marketing across Fintech, Transportation, Data Warehousing and Health. He promises he’s not as boring as he sounds; Follow him on Twitter, @dylanlacey, and he’ll prove it!

[WORKSHOP] Run Your Tests Anywhere

Abstract
Do you have a few JavaScript or Java tests and you need your colleague to run them for you? Oh, they don’t have Node or Java installed? What to do? Docker is the solution!

Run your tests on your laptop, on your colleague’s laptop, run them on a local or a remote Continuous Integration server (CI). Combine Docker with your tests to avoid the dependency hell and enable anyone, anywhere to run them. Docker is commonly seen as a tool to package and deploy applications to different environments, but it is very useful in testing frontend and backend applications.

Putting your tests inside a Docker image can be daunting at the beginning, but a basic understanding of how Docker works, how to create Docker images and run Docker containers will enable us to run our tests anywhere.

This workshop will show you great foundations and concepts to run tests (and potentially any application) in Docker, which you will learn through practical exercises. We will go in detail through the process of putting a test suite in Docker, from creating the Docker image and running it locally to the point where we run our tests on a complete new CI. We will cover the common pitfalls when using Docker and best practices to build good Docker images and run stable Docker containers in different environments.

Outline

• Introduction and quick environment check
• Docker introduction
• Introduction to our testing application (to be used along the workshop)
• Putting the application in Docker and running it, as a practical exercise
• Writing a few tests to test our sample application and using Docker to run them inside a container
• Run multiple Docker containers via docker-compose to test our application in different environments
• Running tests in a continuous integration pipeline
• Wrap up

Learning Outcomes

• Get insights on how an application can be containerized to make testing easier
• Scale-up test suites by running them in parallel and in different environment combinations
• Orchestrate multiple Docker containers to simplify test setup and execution
• Integrate the different elements from the training to build test setups that fit better your web application testing needs
• Identify and put together all the moving pieces of the test setup to facilitate the configuration of a continuous integration pipeline

Bio
Eli is a Software Engineer and a teacher at heart. She enjoys learning new things, both on the technical and human side, and sharing them with the community. She loves to participate and coach at workshops that inspire people from all walks of life to fall in love with programming, such as Django Girls and codebar. She is part of the Leadership Team of Women Who Code Berlin.

[WORKSHOP] Automation Best Practices

Abstract
In this four-hour workshop, you will learn the most important and innovative automation best practices. You will take a bad suite of tests and use best practices to create a suite that can run cross-browser, in massive parallel, through a Continuous Integration pipeline on every commit. You will also learn how to shift-left as you learn how and when it’s appropriate to write lower level tests like API and unit. Furthermore, you will add visual and performance tests where appropriate. All of this is complete with lots of games and challenges and fun.

Outline

• What makes a good automated test
• How to create good page objects
• How to create resilient tests
• How to create automated atomic tests
• How to correctly test login, links, tabs and much more
• How to properly execute your test automation in massive parallel
• How to integrate your automation into a CI pipeline
• How to do automated visual testing
• Front-end performance testing
• Cloud-grid execution

Learning Outcome
By the end of this workshop you will have a deep understanding of how to test a web application by shifting-left and right. You will use multiple types of tests such as functional UI, API, visual, and performance to cover many testing gaps. You will also do this in a CI environment using industry best practices.

Bio
Enrique helps customers with all their Sauce testing needs by being a leader in our Support team. He has a passion for not only solving customer’s issues but sharing knowledge to improve the experience of all our users.

[WORKSHOP] Build an API and an API Testing Framework From Scratch in 120 Minutes

Abstract
Curious about how a REST API is created? Or curious about you might write automation to test it? In this workshop, we will go from a blank file to working REST API with a scalable automated test framework in 120 minutes! The API and test framework will be written using Python, a popular back-end language for many web applications.

Learning Outcomes

• Learn how to create and deploy an API-based web app using Flask in Python
• Understand some basic principles of creating a REST API
• Understand the benefits of using requests, an excellent Python library for web requests
• Learn how to build a scalable API test framework using Python and requests

Bio
Evelyn is a Solutions Architect specializing in Sauce Labs connectivity solutions (Sauce Connect Proxy, IPsec). In her previous role as a Customer Success Manager Evelyn had the privilege to work with almost all the U.S. Sauce Labs customers. During that time she developed a deep understanding of the challenges faced in test automation and an appreciation for the craft. When she’s not learning or sharing knowledge she enjoys hard Sci-Fi and Formula 1.

[WORKSHOP] Crafting a Test Framework

Abstract
If you have ever maintained a Selenium test suite, you know that the most expensive piece is dealing with the maintenance costs, not the creation or execution costs. There are straightforward ways to leverage your framework to minimize flakiness and make it easier to update your test code only when needed. We’ll walk through testing a sample real-world application focusing on how each of the components work together.

Outline/Structure

• Writing good tests
• Using Test Data
• Working with Page Objects
• Managing Synchronization
• Encapsulating Objects
• Executing Tests at Scale

Key Takeaways

• What to prioritize when developing test tooling
• How different framework components work together

Bio
Eyal Yovel is a Solutions Architect at Sauce Labs based in London, UK, where he works with organizations across EMEA and the US to improve their testing practices and get the most value out of their investment in Sauce Labs. He has over 15 years of experience in software development and software automation. In that time, his roles combined coding, mentoring, consulting, and advanced troubleshooting in test frameworks across a wide range of environments and automation frameworks.
He has a passion for learning new technologies and new test frameworks.

[Workshop] Run Cypress Tests on Sauce Labs Using Sauce Control

Abstract
Test Automation would be a lot easier without having to manage so many libraries, plugins, and tools to get your test environment working. Learn about how Sauce Control makes it easy to utilize a Docker container or Sauce Labs Virtual Machines (VMs) for test environment setup, and get started writing Cypress tests in minutes.

Learn the SauceCTL command line interface basics and install the toolkit, understand the structure of a Sauce Control Cypress project, and make a couple simple modifications to configuration files. Add some simple tests, and see what you can do with Cypress tests in the Sauce Labs dashboard. In under two hours you’ll be ready to run your tests locally and in a virtual environment, and be ready to writer a Cypress test suite taking advantage everything that using Cypress with Sauce Labs dashboard and insights offers.

By allowing Sauce Control to manage the complexities of your test environment, you can make a few simple modifications to your Sauce configuration file and access an up-to-date working environment with the ease of writing Cypress code and tests on a wide range of desktop browsers.

Learning Outcomes

• Understand how to install and configure Sauce Control with Cypress
• Understand the use case and advantages in creating Cypress Tests on Sauce Labs

Bio
Félix is a Senior Software Engineer at Sauce Labs. He was formerly a DevOps engineer and moved to software engineering a couple of years ago. He has worked in many different areas including online retail, ride-sharing and even as assistant head of studies at a French IT college. Félix has too many interests to list, however his top two are exploring aeronautic and energy topics.

Testing Across the Stacks: An Intro to Testing Both the UI and API Layers Together

Abstract
Web services and APIs make up a huge chunk of the code in the applications we test, but either we’re not aware of the APIs or we’re asked to focus on the user interface instead. If you only focus on UI testing, you may be missing something big: APIs are where all of the business logic for the application is exposed—and they can hide some pretty nasty bugs. Web services and APIs can be tested in isolation, but they can also be tested in combination with the UI. Understanding how the UI and API work together can make it easier to troubleshoot when things go wrong from the UI. This understanding can also give you a more complete picture of the application under test.

Key Takeaways:

• Why web services and APIs are important to test
• How HTTP Response Codes fit in to your testing
• How familiar UI tests translate to API tests
• How to find the API calls your UI is making

Bio
Hilary Weaver-Robb is a software quality architect at Detroit-based Quicken Loans. She is a mentor to her fellow QA team members, makes friends with developers, and helps teams level-up their quality processes, tools, and techniques. Hilary has always been passionate about improving the relationships between developers and testers, and evangelizes software testing as a rewarding, viable career. She runs the Motor City Software Testers user group, working to build a community of quality advocates. Hilary tweets (a lot) as @g33klady, and you can find tweet-by-tweet recaps of conferences she’s attended, as well as her thoughts and experiences in the testing world, at g33klady.com.

Journey to Test Automation: Get Kicked in the A** Then Move On!

Abstract
Traditional organizations who want to move on DevOps don’t necessarily figure out what changes are required to start doing test automation. Because of lack of experience, without internal success stories, teams struggle to initiate the right change and may lose time and money by doing the wrong thing.

An expert group assisting the organization can help, as an eye-opener of course, but it does not solve the entire problem: many attitudes and changes within the dev/qa teams are key factors for a success. Creating a safe zone for experimentation, encouraging training and having affirmed support of management, are some of the behaviors we did experiment, and which brought success.

In this duet presentation – the QA lead of the team, and the lead of the expert coaching group – you will discover how this team did the turnaround to move to a mature practice of test automation. In addition, you will learn how a localized success like this one has been leveraged by the rest of the organization.

Key Takeaways:

• Learn where to start if you want to introduce Continuous Testing in your organization
• Get some tips like events, attitude, and success factors for this journey
• Avoid some pitfalls – you already know them, but be sure not to jump anyway

Bio
Henri Bigot has been an IT professional for nearly fifteen years. He is dedicated to team management and the achievement of ambitious goals. He strongly believes in human value, rather than tools or processes. Today, he leads an enthusiastic team of software test developers. During his career, Henri has created rich and varied opportunities for himself. He has worked in Europe, Asia and North America, where he has been able to immerse himself in different cultures, and is one of the co-authors of “The Missing Link,” a novel about Continuous Testing.

Include Service Virtualization and Make Native App Automation Rock Solid

Abstract
In UI Automation, stability of an underlying API is quite important. An unstable API leads to flaky and unreliable UI tests. Most teams aim for high speed and continuous delivery but flaky UI Automation is a big obstacle to achieve this aim.

How to tackle this common problem? One known solution is “Testing in Isolation” by removing dependency on the underlying API. The API dependency can be removed by virtualizing underlying API responses (aka Service Virtualization). The Innovapost team used wiremock as a mock server to implement service virtualization. They introduced service virtualization for Android and IOS App Automation and got wonderful results in achieving reliable test results.

Key Takeaways:

• What is Testing in Isolation and why it is important in UI Automation
• What is the Service Virtualization and how to implement it using wiremock
• How to implement Service virtualization for Android and IOS APP Automation
• Extend CI/CD pipeline to include Service Virtualization

Bio
Jagmit has 12+ years of IT experience across development and testing roles across industries including healthcare, media, logistics and finance. As a Senior Automation Engineer/Consultant at Innovapost where he is responsible for designing test automation frameworks for Web and Mobile applications using a different set of tools and languages. When he is not working on automation he enjoys playing racket sports, hiking and skiing.

[WORKSHOP] Run Cypress Tests on Sauce Labs Using Sauce Control

Abstract
Test Automation would be a lot easier without having to manage so many libraries, plugins, and tools to get your test environment working. Learn about how Sauce Control makes it easy to utilize a Docker container or Sauce Labs Virtual Machines (VMs) for test environment setup, and get started writing Cypress tests in minutes.

Learn the SauceCTL command line interface basics and install the toolkit, understand the structure of a Sauce Control Cypress project, and make a couple simple modifications to configuration files. Add some simple tests, and see what you can do with Cypress tests in the Sauce Labs dashboard. In under two hours you’ll be ready to run your tests locally and in a virtual environment, and be ready to writer a Cypress test suite taking advantage everything that using Cypress with Sauce Labs dashboard and insights offers.

By allowing Sauce Control to manage the complexities of your test environment, you can make a few simple modifications to your Sauce configuration file and access an up-to-date working environment with the ease of writing Cypress code and tests on a wide range of desktop browsers.

Learning Outcomes

• Understand how to install and configure Sauce Control with Cypress
• Understand the use case and advantages in creating Cypress Tests on Sauce Labs

Bio
James Tacker is one of the lead contributors in terms of documentation and training at Sauce Labs, and spends most of his time maintaining the sauce-docs platform. James is passionate about imparting practical technical knowledge with regards to the Sauce Labs platform and he currently works as a Senior Technical Content Writer for the Technical Content Team in Product.

Implementing CI/CD with Mobile in Mind

Abstract
Setting up CI/CD itself is a challenging task, especially if you are starting from scratch. Implementing one for mobile apps has its own complications, such as signing the apps and running tests on devices/simulators.

In this talk, Jaswanth will talk about the best way to set up mobile app build pipelines from scratch. In order to view an end-to-end example, he will show how to build an android and iOS app pipeline of the SwagLabs react native app (https://github.com/saucelabs/sample-app-mobile).

Key Takeaways:
After listening to this talk, you will be able to set up a CI/CD pipeline that can do the following:

• Build a react native app
• Setup appropriate build triggers
• Run unit and UI tests
• Send build notifications
• Build and publish the android app
• Build and publish the iOS app

Bio
Jaswanth Manigundan is a developer turned tester. Even though writing code to build applications is so much fun, his now best friend showed him a few years ago that helping write good quality apps is much more fun. Jas jumped into testing from being a developer and has never looked back. He is very passionate about native mobile testing frameworks, especially Espresso (Android), XCUI testing (iOS) and Detox (React Native)

Setting Up Your Tests To Fail

Abstract
It’s a fact of life that we often have to write automated UI tests for features that have defects, or that interact with 3rd party APIs that aren’t returning the right responses, or for items that we know aren’t working right. When the team has decided that the behavior isn’t going to be fixed, what’s an automation engineer to do? Let the tests fail? Not write them? Champion harder for the defects? Jenny Bramble suggests writing your tests to pass. By creating tests that pass on the current expected behavior (the defect), we are in a perfect position to tell when the defect is resolved, or the API is returning the correct information, or any of the other error cases we may be encountering. This prevents failure fatigue (from seeing a test always fail), while still providing meaningful, actionable information out of our test suite.

Jenny will discuss several cases that she’s experienced that this method has worked for as well as how to keep the rest of the team informed through TODOs, Jira stories, and documentation. And—of course!—what to do when your test finally fails. You’ll walk away from this talk with a clear idea of when to design your tests to fail, how to use TODOs and other indicators to let the rest of the test team know what’s going on, as well as a frank discussion of automation as information—not as a bug detection system!

Key Takeaways:

• Automated tests are information, not bug detection systems
• Automated tests should pass on EXPECTED behavior even if that behavior is objectively a defect (AKA designing to fail)
• TODOs, documentation, and other methods to keep your team informed of the expected behavior of your automation suite

Bio
Jenny came up through support and DevOps, before diving headlong into her career as a tester. Her love of support and the human side of problems lets her find a sweet spot between empathy for the user and empathy for her team. She’s done testing, support, or human interfacing for most of her career. She finds herself happiest when she’s making an impact on other people—whether it’s helping find issues in applications, speaking at events, or just grabbing coffee and chatting.

How AI Is Impacting Software Testing

Abstract
Decades of research on artificial intelligence and software testing have produced a rich set of technologies for autonomous testing. AI-driven test methodologies can now take advantage of synthetic test data, automatic test case generation, and even AI-driven automatic bug fixing.

Join Jim Whitehead, Professor of Computational Media and Chief Scientist at AutonomIQ, and Ram Shanmugam, CEO of AutonomIQ, as they discuss how the artificial intelligence technologies of synthetic test data generation, reinforcement learning, and automatic bug fixing will transform the landscape of web and mobile application testing.

Key takeaways:

• Different approaches for synthetic data generation and their application
• How reinforcement learning can generate automatic test cases
• Overview of how automated bug fixing works
• Roadmap for when AI testing technologies will see widespread use

Bio
Jim Whitehead brings over 25 years of experience as a software engineering and artificial intelligence researcher to his role at AutonomIQ. In software engineering, he performed early research using machine learning techniques to predict whether commits are buggy (just in time bug prediction). His computer games research focuses on artificial intelligence techniques for creating computer game content (procedural content generation). The unique synergies between computer games and software engineering research drive many research insights at AutonomIQ.

The Future of Sauce

Abstract
Join John Kelly and Matt Wyman as they discuss the influence of modern software trends and their effects on the future of testing.

Bio
John Kelly is Chief Technology Officer for Sauce Labs, where he is responsible for defining the company’s long-term technology strategy while ensuring the continued delivery of near-term product innovation to customers. Kelly also oversees the company’s recently established Open Source Program Office. A technology industry veteran with more than 25 years of experience, Kelly has extensive expertise in areas critical to the present and future of automated testing and application quality, including open source, machine learning, analytics, and security, as well as deep knowledge of cloud-based ecosystems. He has held executive leadership positions spanning R&D, product management, engineering, and business development across a number of technology companies ranging from startup to Fortune 500.

[WORKSHOP] Build an API and an API Testing Framework From Scratch in 120 Minutes

Abstract
Curious about how a REST API is created? Or curious about you might write automation to test it? In this workshop, we will go from a blank file to working REST API with a scalable automated test framework in 120 minutes! The API and test framework will be written using Python, a popular back-end language for many web applications.

Learning Outcomes

• Learn how to create and deploy an API-based web app using Flask in Python
• Understand some basic principles of creating a REST API
• Understand the benefits of using requests, an excellent Python library for web requests
• Learn how to build a scalable API test framework using Python and requests

Bio
Josh Grant is a test automation professional who has worked in this space for over nine years. In that time he has worked on automation at all levels, in a variety of languages, frameworks and organizations. Currently he is a Senior Solutions Architect at Sauce Labs, helping enterprise teams succeed with their test automation. He is based in Toronto, Ontario.

Hunger is the Best Sauce: GetWellNetwork’s Voyage Into Mobile Automation Using Sauce Labs

Abstract
GetWellNetwork produced its first iOS and Android mobile applications and the team quickly needed a way to test their software on various device/OS combinations. They already used Katalon (for their automated tests) and GitLab-CI (for their CI/CD pipeline), and they needed to figure out a way to expand that to include mobile automation. After evaluating a number of different tools, the team chose Sauce Labs as a partner and began to build mobile automation from the ground up. After about six months, they achieved the following results:

• Their apps are automatically uploaded to Sauce Labs when the Mobile Development team releases them to staging as part of a GitLab-CI pipeline (will show code)
• Katalon test cases/suites that run nightly to validate key pieces of the app (login, forgot password, etc) on various device and OS types and proactively inform us if anything has broken. They designed these test cases in a way that they work on either iOS or Android to eliminate need for maintaining separate test cases for each (will show code)
• Various profiles (equivalent of a Sauce Labs deviceID) to ensure they are getting wide coverage for our tests
• Custom methods created for performing things like swiping up/down/left/right using Appium on any device type with any resolution (will show code)
• Plans to expand their test case coverage and device coverage

An attendee will leave this session with better knowledge of how to build mobile automation on Sauce Labs from the ground up!

Key Takeaways:

• How the GetWellNetwork team stood up mobile automation testing from the ground up using Sauce Labs real devices
• How they are utilizing DRY programming practices by developing tests that can:
• run on either iOS or Android
• run on multiple device types in parallel with the click of a button
• How they handled things like scrolling actions based on screen resolution
• How they sped up the testing process by creating a continuous delivery pipeline to auto-upload our app to Sauce Labs when released by the mobile development team
• The team’s plans to enhance our CI/CD pipeline

Bio
Joshua Young is an IT Professional with 11 yrs of experience in software development for a market-leading patient engagement health software company. Joshua has managed multiple teams across a span of departments including Product, Client Services, and QA as his company successfully completed 4 acquisitions and grew from 45 employees to over 350 in the span of 10 years. Most recently, Josh has been leading the QA Engineering Department and in charge of building an automation infrastructure from the ground up.

Move Forward With an Effective Test Automation Strategy

Abstract
Automated tests are generally introduced into a project to solve issues such as repetitive manual work, working with large data sets, or getting faster feedback in a CI/CD pipeline. Whatever the reason, creating a test automation strategy is a critical step to ensuring higher Return On Investment (ROI), more test coverage, increased test reliability.

However, without a proper automation strategy you may be left wondering what tools to use, what test to automate and what team members to use. This will affect the return you get after spending hours and months on writing automated tests.

A test automation strategy guides you into implementing test automation in a way that is repeatable. It helps you identify the goal (why), who is the team, how you will be doing the test automation (tools), when and where you will automate and very importantly WHAT you will be automating. This is important as while test automation significantly expands test scope and coverage, automating EVERY test will take more cost, effort, and time than is practical.

In this talk, Julia Pottinger will guide you through creating a test automation strategy that will help to ensure a higher Return On Investment (ROI) while answering critical questions that will help to provide clarity to you and your team.

Key Takeaways:

• Understanding the importance of having an automation strategy
• A set of questions to help you understand and create an automation strategy
• Create a test automation strategy that is understood by your team to ensure a higher Return On Investment(ROI), more test coverage, increased test reliability.
• Identify why you want to do test automation. This will impact and help you define who will be creating and maintaining the automated test, the tests you automate as well as the tools that you use.

Bio
Julia Pottinger is a Training and Development Manager at QualityWorks with expertise in manual, automated and API testing and training. She is passionate about sharing her knowledge and experience and contributes to the testing community through writing articles, and delivering testing content on Test Automation University as well as her Youtube Channel and blog. She also conducts testing bootcamps for persons interested in entering the field of QA.

secure.AllTheThings() – Make Security Accessible to Everyone!

Abstract
Security signals are critically important to ensure the quality and stability of code, especially in production environments (or in CI/CD pipelines). A lack of visibility into security weaknesses in code can represent a significant threat. Wouldn’t you want to know about potential security flaws in your code as early as possible?

While tooling in various areas flourishes, from static code analysis to unit and functional testing, security frameworks often have been limited to subject matter experts, rarely used by developer and QA teams and audits, if at all, run at the very end of the software development lifecycle. With the shift-left spirit we believe this has to change. Adding security checks early to your pipeline can save time and brings awareness and exposure of vulnerabilities to developers which ultimately is the silver bullet for security in your company.

In this session, Justin Dolly, Chief Security Officer, and Christian Bromann, Staff Software Engineer of the Open Source Program Office at Sauce Labs, will give exclusive insights on a new platform and a new set of tools designed to test the security of your applications in a simple, effective and very accessible way.

Bio
Justin Dolly is Chief Security Officer at Sauce Labs, where he oversees the development and implementation of the company’s long-term security strategy, ensuring its customers have the highest level of protection to support their digital goals. He is a Certified Chief Information Security Officer (CCISO) with more than 20 years of experience in building and implementing a culture of security within global organizations.

Your Code Will Die in a Fire

Abstract
Not to be dramatic, but it’s true. We have all shipped bugs or taken production down. Or both. At the same time. This talk is about the methods for lowering the likelihood of our work breaking things and being ready for when it does.

This session will cover:

• Your code will die in a fire: Planning your work with failure in mind
• Making sure the fire doesn’t get out of control: Dealing with errors so your user doesn’t see the worst
• Minimizing the likelihood of fire: Testing for planned and unplanned errors
• Seeing the smoke before the fire: Logging and monitoring

You will walk away with a mental framework and concrete steps for increasing the resilience of your code.

Key Takeaways:

• The importance of planning work with failure in mind
• How to remediate errors to ensure optimal user experience
• Strategies for just enough testing

Bio
Kate Green is an engineering leader with over 20 years in the industry. She’s worked in just about every part of the stack: front end, back end, QA, automation, and site reliability. Her favorite code to write is tooling for other engineers to help them work more efficiently.

As a leader, she is focused on her people. An educator by training, she’s captivated by figuring out how to help each engineer she leads to be their best. She’s a mentor, teacher, and planner who understands we all need focus and time to think to be productive.

In her spare time, she applies the same principles in her talk to her hobbies: dog agility, gardening, and doing puzzles. She also spends a lot of time asking her 3 and 5 year old lots of “why” and “how” questions. They will someday be great problem solvers, too.

Testing in Production – Canary Releases at Netflix

Testing in Production effectively and safely requires a significant amount of automation, strong monitoring capabilities and resilient deploy pipelines. Testing in production is done in a multitude of ways across the industry: canarying, A/B testing, Feature Flags or a combination of these are the most popular. The Netflix website team uses all three of these in analyzing real user experience in production. In this session, we will touch base on these three strategies, but dive deeper into the canary process, how that is implemented and how it’s baked into the website’s release process.

Key Takeaways:

• Key components that make testing in production a reality at Netflix.
• Understand the implementation and criticality of canaries in product releases.
• Strategies to minimize blast radius (impact) and duration of the impact, esp. for the “not-so-happy” canaries.
• Learnings – Do’s, Don’ts and Risks that we need to consider for testing in Production.

Bio
Kranthi is a Senior Site Reliability Engineer in the Website tooling and delivery team at Netflix. With more than 10 years of experience working for Netflix and previously Microsoft, she has a passion for customer experience and continuous delivery. At Netflix she focuses on building release pipelines for website teams enabling them to release more frequently, safely and reliably.

DEMO | Maximizing the ROI of Your Salesforce Testing with AutonomIQ

Abstract
Used in over 80,000 organizations worldwide, Salesforce is the most widely adopted CRM system. Conducting automated functional testing is challenging in Salesforce, however, given that the web pages are dynamic.

In this demo session, Krishna Srinivasan will demo hands-on use cases of testing the Salesforce application and show how you can customize the in-built SDFC (Salesforce Dot Com) features. You’ll learn how to build a robust testing framework that will give you reassurance even if you have no previous experience.

Key Takeaways

• Why use autonomous testing for Salesforce
• How to create robust test assets with no code
• How autonomous testing fits within your CI/CD pipeline

Bio
Krishna Srinivasan is the Founding Engineer and the Director of Products at AutonomIQ. Upon receiving his BTech from NIT Nagpur and his Masters in the US, he began his career with National Semiconductor and Texas Instruments. There, he designed and architected applications used by hundreds of thousands of Electrical Engineers around the world for designing circuits using TI’s microprocessors. A few of these applications include designing LED related circuitry used by light designers, IoT related circuitry used by sensor designers, etc. He then joined AutonomIQ as the Founding Engineer and continues to lead the Product initiative and works closely with customers to drive adoption of the product.

DEMO | Scaling Cypress, TestCafe, Playwright, and Puppeteer Tests on Sauce Labs

Abstract
In this demo Kunal Jain, Director of Product Management at Sauce Labs, will show you how to use new Sauce Labs capabilities to run your JavaScript tests at scale on Sauce Labs, while accessing test insights.

In recent years, there’s been a shift towards JavaScript test automation frameworks. Today many Sauce Labs customers are using Cypress, TestCafe, Puppeteer, and most recently Playwright. If you’re using these frameworks for all your testing needs, or as a part of your overall testing strategy, then join the demo to learn how to:

• Speed up tests through mass parallelization
• Leverage test assets and insights for better debugging
• Build a single cross-framework solution for cross-browser testing
• Make testing collaborative

Bio
Kunal is Director of Product at Sauce Labs. Previously, he worked at CircleCI where he was responsible for the developer experience and insights offerings. Besides shipping capabilities to customers, he was part of the end of life initiative to decommission CircleCI’s older platform. Before CircleCI, he was at ThoughtWorks where he played multiple roles (quality analyst, agile coach, and product manager) across multiple geographic locations. When he is not at work, you can find him hiking somewhere in the Bay Area, making coffee, or planning his next trip.

Testing a Data Science Model

Abstract
In this session, Laveena Ramchandani will help inspire testers to explore data science models. A model is a statistical black box, so how can we understand its behaviours to test it properly? Data science teams may or may not have testers testing the models so how can we be confident that what is produced is good enough?

This is an exciting and emerging area for testers. Laveena will share how she explored the world of data science when testing a model and how other testers can apply this knowledge. She will go through her journey of discovering data science model testing. Attendees will find her session useful not just for testing a data science model, but also in their day-to-day testing efforts as well.

Key Takeaways

• Understand what data science is and how testers can get involved to add more quality
• Learn how to test models, validate them, and understand the results
• Identify existing skills that can be applied in a data science team
• Understand how to structure teams to increase confidence in the data produced and help clients make better decisions

Bio
Laveena Ramchandani is an experienced Testing Consultant with a comprehensive understanding of tools available for software testing and analysis. She aims to provide valuable insights that have high technical aptitude and hopes to inspire others in the world through her work. Laveena holds a degree in Business Computing from Queen Mary University of London and regularly speaks at events on data science models and other topics.

Continuous Performance Testing in DevOps

Abstract
Performance testing isn’t the first thing organizations think about when moving to DevOps – in fact, it’s often ignored as traditional approaches don’t jive well with the fast and nimble world of DevOps. However, performance is still a critical part of the user experience, and poor performance and outages will quickly negate the value of the features you’re delivering.

Lee believes that organizations don’t have to gamble with application performance. He will discuss techniques for implementing continuous performance testing in your pipeline, so you don’t have to roll the dice on your user experience. Topics will include performance testing activities at each stage of the pipeline – from the unit level through testing in production. You will also learn how to rethink your approach to performance testing and work with your DevOps practices instead of against them in areas like test environment and data management.

You’ll walk away with a new outlook on performance testing in DevOps and ideas you can begin to implement in your pipeline.

Key Takeaways:

• Understand why traditional performance testing approaches don’t fit well with agile and DevOps development processes
• Learn techniques for shifting performance testing and analysis activities both left and right in the development pipeline
• Form a new way of thinking about performance testing that is better aligned with DevOps practices

Bio
Lee Barnes has over 25 years of experience in the Software Quality Assurance and Testing field. Lee has been involved in the implementation of test automation and performance testing solutions in hundreds of environments across a wide array of industries. Most recently, he’s been involved with bringing quality practices (with a focus on automation and performance) to DevOps teams.

Lee regularly speaks at industry conferences including DevOpsDays, Agile+DevOps East, STPCon, and QUEST.

[WORKSHOP] Run Cypress Tests on Sauce Labs Using Sauce Control

Abstract
Test Automation would be a lot easier without having to manage so many libraries, plugins, and tools to get your test environment working. Learn about how Sauce Control makes it easy to utilize a Docker container or Sauce Labs Virtual Machines (VMs) for test environment setup, and get started writing Cypress tests in minutes.

Learn the SauceCTL command line interface basics and install the toolkit, understand the structure of a Sauce Control Cypress project, and make a couple simple modifications to configuration files. Add some simple tests, and see what you can do with Cypress tests in the Sauce Labs dashboard. In under two hours you’ll be ready to run your tests locally and in a virtual environment, and be ready to writer a Cypress test suite taking advantage everything that using Cypress with Sauce Labs dashboard and insights offers.

By allowing Sauce Control to manage the complexities of your test environment, you can make a few simple modifications to your Sauce configuration file and access an up-to-date working environment with the ease of writing Cypress code and tests on a wide range of desktop browsers.

Learning Outcomes

• Understand how to install and configure Sauce Control with Cypress
• Understand the use case and advantages in creating Cypress Tests on Sauce Labs

Bio
Lindsay is a technical trainer and educator hailing from Austin, TX. She has spent the last 10+ years working in the technology space, striving to learn and teach technical subjects. With a Master’s Degree in STEM Education from UT Austin, Lindsay has experience researching how people learn and build knowledge and skills, and years of experience creating learning content that allows others to gain technical skills and write code.

Lindsay enjoys exploring solutions to novel problems, from game design, to software testing, to learning new dance moves, and has years of experience creating courses and technical content about coding and technology.

Building an API Testing Strategy

Abstract
Web APIs are everywhere. Whether you’re filing your taxes or hailing a taxi, Web APIs drive the services we use. And as they’ve grown in popularity in software architectures, they’ve also grown in complexity. The increase in complexity means teams need a robust testing strategy to handle the many risks that can impact our Web API platforms. But where do we start? What testing do we need to do? What opportunities are available to us?

This talk explores the goal of a good testing strategy to help you choose the right approach for your API testing. We’ll explore the different API testing activities available to us and how understanding our testability can inform our API testing strategy. By the end of this talk, you’ll be able to:

Key Takeaways

• Illustrate a model for the thinking about the role of testing
• List different approaches to testing APIs
• Relate certain testing activities to the mitigation of specific risks
• Use testability models to select suitable testing activities

Bio
Mark Winteringham is a tester, toolsmith and the Ministry of Testing DojoBoss with over 10 years experience providing testing expertise on award-winning projects across a wide range of technology sectors including BBC, Barclays, UK Government and Thomson Reuters. He is an advocate for modern risk-based testing practices and trains teams in Automation in Testing, Behaviour Driven Development and Exploratory testing techniques. He is also the co-founder of Ministry of Testing Essentials a community raising awareness of careers in testing and improving testing education. You can find him on Twitter @2bittester or at mwtestconsultancy.co.uk / automationintesting.com

The Future of Sauce

Abstract
Join John Kelly and Matt Wyman as they discuss the influence of modern software trends and their effects on the future of testing.

Bio
As a twenty-year veteran of entrepreneurship, Matt has partnered to develop multiple startups into stable value centers in both the Head of Engineering and Head of Product roles. Matt’s passion is with forward-leaning technology and the application of lean practices in product, data, and design. DevOps is near and dear to Matt’s heart. Matt lives in Half Moon Bay and loves to mountain bike and play tabletop games with his family.

Help, My Test Automation is Turning on Me!

Abstract
We can look at test automation as a cycle which keeps repeating itself:

1. Write or update a test
2. Code or update the test automation code
3. Review the newly added code
4. Deploy & share the results

If one of those steps in the cycle goes wrong, and they will, we can get stuck in a loop. During this presentation, Michel Lalmohamed will tackle several issues he encountered during his 10-year career for each step of the cycle and show what he did to fix them. Instead of starting at step 1, he will take a brief look at the last step in the cycle. Michel will discuss the topic of consistent red builds / failed tests. Anybody who has done anything with test automation can relate to the phenomenon of consistent failed tests and how they can kill the test automation momentum. However, the fix for these failed tests can lie in any of the four steps mentioned above. Getting the build green will stay the main focus throughout each discussed step in the cycle.

Key Takeaways:

• Learn how to ensure failed tests don’t impact the overall test automation value in a project
• Be able to implement improvements to existing test automation code and the review process
• Know how to set up a strategy for a more stable test automation effort
• Understand that the test automation effort is not only the responsibility of the testers—it must be shared

Bio
Michel Lalmohamed is a senior mobile and web automation consultant at Valori Fullstack Testing where he builds test automation solutions custom made for several clients. He has been in the test automation game for 13 years. Michel loves to automate everything and shares this passion by coaching test engineers and teaching several technical courses.

[WORKSHOP] Automation Best Practices

Abstract
In this four-hour workshop, you will learn the most important and innovative automation best practices. You will take a bad suite of tests and use best practices to create a suite that can run cross-browser, in massive parallel, through a Continuous Integration pipeline on every commit. You will also learn how to shift-left as you learn how and when it’s appropriate to write lower level tests like API and unit. Furthermore, you will add visual and performance tests where appropriate. All of this is complete with lots of games and challenges and fun.

Outline

• What makes a good automated test
• How to create good page objects
• How to create resilient tests
• How to create automated atomic tests
• How to correctly test login, links, tabs and much more
• How to properly execute your test automation in massive parallel
• How to integrate your automation into a CI pipeline
• How to do automated visual testing
• Front-end performance testing
• Cloud-grid execution

Learning Outcome
By the end of this workshop you will have a deep understanding of how to test a web application by shifting-left and right. You will use multiple types of tests such as functional UI, API, visual, and performance to cover many testing gaps. You will also do this in a CI environment using industry best practices.

Bio
Nikolay Advolodkin is a Senior Solutions Architect at Sauce Labs. He has an extensive background in software testing, quality assurance, and test automation as the CEO and Test Automation Instructor at UltimateQA.com, a training site full of videos and resources covering the gamut of testing topics and technologies.

Nikolay has taught more than 50,000 students in over 120 countries about test automation. He is a frequent contributor to open source and was selected as one of the top automation engineers in the world three years in a row by TechBeacon.com.

Selenium, Playwright, Puppeteer, or Cypress: How To Choose?

Abstract
Cypress is getting a lot of buzz as a way for JS developers to create UI tests. But is it better than Selenium? Not to be outdone, Microsoft forked and released a new version of Puppeteer, called Playwright, with added capabilities. What are the distinctions, and how do you choose?

In this talk, we will compare those test automation frameworks, demonstrating the differences. You will learn some of the critical limitations and benefits of each platform to inform your decision better.

Key Takeaways:

• Critical differences and limitation of these platforms
• How to choose the platform that best suits your needs
• Alternative approaches to solving web UI testing challenges

Bio
Oren Rubin is the founder and CEO of Testim, an AI-based test automation platform that speeds the authoring of resilient end-to-end tests. Oren has over 22 years of experience in the software industry, building mostly test-related products for developers at IBM, Wix, Cadence, Applitools, and Testim.io. In addition to being a busy entrepreneur, Oren is a community activist and the co-organizer of the Selenium-Israel meetup and the Israeli Google Developer Group meetup. He has taught at Technion University and mentored at the Google Launchpad Accelerator.

[WORKSHOP] Improving SLA Performance: QAs Should Own API Monitoring

Abstract
Too often, when a business-critical app or web service goes down or fails to function correctly, it is difficult to pinpoint the source of the problem. One reason for this is that Developers, QA, and monitoring teams may be working in silos, and lack visibility across the entire org.

In this workshop, hear Patrick Poulin, VP of API Testing at Sauce Labs, discuss how leaders are transforming the SLA performance of API programs by making a simple but vital change in operations: unify QA teams while empowering them to own uptime monitoring. After all, QAs are best equipped to reuse functional tests written with high domain knowledge as monitors that can run with much higher integrity and reliability in production and live environments.

To help you get started, the workshop will break down how to transition to a hybrid UI/API testing strategy that will support proper shift-right testing and monitoring of business-critical APIs.

Outline

• The Fast Track to Functional Uptime Monitoring: Meet Patrick Poulin of Sauce Labs and hear how much API testing and monitoring have improved and will continue to improve in the race for quality at speed.
• New Rules for Quality (presentation): See why human error is behind 95% of errors that manage to go undetected until production, or worse, until a customer or cybercriminal discovers the live error.
• Dangerous Bugs that UI Testing Alone Could Not Diagnose (presentation): Hear real examples of how hybrid UI/API testing expands coverage. Also learn how proper API monitoring can enhance API observability to help diagnose issues such as session or memory leaks.
• Demo: Watch us convert an API functional test that was created in the prior workshop into a functional uptime monitor that is capable of going beyond uptime monitoring, and can check an entire API consumer flow without causing latency or bandwidth issues.
• Checklist: Complete a Best Practices Checklist for API Functional Testing and Monitoring for QA/testers.
• Q&A: 20-30 minutes of live questions regarding your checklist or our presentations.

Learning Outcome
Gain QA confidence to deploy modern API monitors that do a much better job of maintaining SLA performance. See results quickly: higher quality code in faster release cycles with shorter testing sprints.

Bio
Patrick Poulin is VP of Product, APIs, at Sauce Labs. Formerly, Patrick co-founded and served as the CEO of API Fortress, an API testing automation platform that was built from the ground up for continuous API testing and unlimited functional uptime monitoring. Prior to API Fortress, Patrick worked as the API evangelist at Getty Images. Before that, he ran the retail vertical for Usablenet where they built the first mobile websites and apps for companies including Tesco, Target, Macy’s, MAC Cosmetics, and 70 other major brands.

[WORKSHOP] Autonomous Testing in Minutes

Abstract
The Autonomous Testing Workshop is tailored for teams who want to seriously reduce the amount of technical work while increasing the effectiveness of creating test cases and executing their tests. This workshop provides hands-on experience with all the activities that typically take place during the set-up, implementation, management, and reporting of test assets. It teaches teams how to leverage state of the art artificial intelligence technology to write and execute Selenium scripts in minutes.

Outline

• Introduction
• Setup environment
• How to create robust test assets autonomously and from plain English
• How to manage and generate useful reports for compliance
• Parallel test execution strategies

Learning Outcome
This workshop will help you accelerate your functional UI testing for web applications from test creation, execution, and maintenance. You’ll learn how to optimize the time it takes for you to build stable test environments to deliver digital confidence across your organization.

Bio
Raj is a co-founder at AutonomIQ and he is enabling the software factories of the future. Prior to AutonomIQ, Raj held SVP & GM roles at CA Technologies, has been the Global Head of Software Quality at NTT Data, and has held product leadership roles at SAP, PeopleSoft (Oracle) and Broadvision.

The 15-Day Test Strategy that Helped Stabilize a Life Insurance Consumer App

Abstract
It’s late in the development cycle and you’re about to launch a new application or push through an important update. But unrelated and unpredictable issues keep showing up! In this case study presentation, find out how Aspire helped one team defeat these issues by implementing a test strategy that stabilized their application in just 15 days.

In this example, the organization’s Life Insurance Quote to Application web portal was delayed from going live due to non-reproducible, intermittent issues that popped up throughout the application. By performing an independent quality assessment of the application, Aspire helped identify a pattern to the issues to determine the root cause and resolve the issues before go-live.

Srinivasan Sankar and Renee Gilmore will share how Aspire worked with the organization to devise and implement a test strategy that accomplished the following within just 15 business days:

• End to End functional testing
• Compatibility testing
• Regression testing (test automation)
• Load/Performance testing

Key Takeaways
In this presentation, you will learn about:

• Techniques that you can employ to test faster without compromising coverage
• The ways in which Process, Technology, and People can come together to accomplish business objectives
• A ‘rare’ Sauce Labs use cases that helped a great deal in the testing process

Bio
Renee Gilmore is the Lead Digital Marketing Specialist with Amica Life and the Product Owner for the direct-to-consumer online application. As product owner for the online application, she was responsible for releasing a product that would increase online engagements and conversions throughout the application process.

[WORKSHOP] Improving SLA Performance: QAs Should Own API Monitoring

Abstract
Too often, when a business-critical app or web service goes down or fails to function correctly, it is difficult to pinpoint the source of the problem. One reason for this is that Developers, QA, and monitoring teams may be working in silos, and lack visibility across the entire org.

In this workshop, hear Patrick Poulin, VP of API Testing at Sauce Labs, discuss how leaders are transforming the SLA performance of API programs by making a simple but vital change in operations: unify QA teams while empowering them to own uptime monitoring. After all, QAs are best equipped to reuse functional tests written with high domain knowledge as monitors that can run with much higher integrity and reliability in production and live environments.

To help you get started, the workshop will break down how to transition to a hybrid UI/API testing strategy that will support proper shift-right testing and monitoring of business-critical APIs.

Outline

• The Fast Track to Functional Uptime Monitoring: Meet Patrick Poulin of Sauce Labs and hear how much API testing and monitoring have improved and will continue to improve in the race for quality at speed.
• New Rules for Quality (presentation): See why human error is behind 95% of errors that manage to go undetected until production, or worse, until a customer or cybercriminal discovers the live error.
• Dangerous Bugs that UI Testing Alone Could Not Diagnose (presentation): Hear real examples of how hybrid UI/API testing expands coverage. Also learn how proper API monitoring can enhance API observability to help diagnose issues such as session or memory leaks.
• Demo: Watch us convert an API functional test that was created in the prior workshop into a functional uptime monitor that is capable of going beyond uptime monitoring, and can check an entire API consumer flow without causing latency or bandwidth issues.
• Checklist: Complete a Best Practices Checklist for API Functional Testing and Monitoring for QA/testers.
• Q&A: 20-30 minutes of live questions regarding your checklist or our presentations.

Learning Outcome
Gain QA confidence to deploy modern API monitors that do a much better job of maintaining SLA performance. See results quickly: higher quality code in faster release cycles with shorter testing sprints.

Bio
Sangit is an engineer by trade, but after some time growing in the adtech industry he saw an opportunity to shift towards a more client facing role. In doing so, he realized his passion for bridging the technical side with the business side. Sangit used this passion to help multiple startups double in size and revenue. His professional experiences have all brought him where he is today. As a Solution Engineer at Sauce Labs, Sangit works with clients and business partners to improve their API testing.

Sangit is an avid traveler and seeks to check off only two more continents from his travel list. He’s also had a lifelong passion for music and enjoys playing clarinet and viola in his free time.

Accelerating Delivery: Automated Tests, 3-fold Benefits

Abstract
Automated Functional Testing, Dynamic Security Scanning and Accessibility Testing are performed as three independent activities. To perform all the three efforts effectively to deliver a high quality product, all the actors require the same level of knowledge about the application.

In this session, Sravanthi will show how to effectively use automated tests to perform dynamic security scanning and accessibility scan as part of automated test execution and generate custom reports, as well as how to leverage results to drive actions with zero manual effort.

Key Takeaways:

• Utilize test automation to help perform more than just feature verification.
• Learn about incorporating accessibility and dynamic security scanning without any additional effort.

Bio
An engineer at heart, Sravanthi Bheemanadham loves to write code, solve problems and think enterprise.

The 15-Day Test Strategy that Helped Stabilize a Life Insurance Consumer App

Abstract
It’s late in the development cycle and you’re about to launch a new application or push through an important update. But unrelated and unpredictable issues keep showing up! In this case study presentation, find out how Aspire helped one team defeat these issues by implementing a test strategy that stabilized their application in just 15 days.

In this example, the organization’s Life Insurance Quote to Application web portal was delayed from going live due to non-reproducible, intermittent issues that popped up throughout the application. By performing an independent quality assessment of the application, Aspire helped identify a pattern to the issues to determine the root cause and resolve the issues before go-live.

Srinivasan Sankar will share how Aspire worked with the organization to devise and implement a test strategy that accomplished the following within just 15 business days:

• End to End functional testing
• Compatibility testing
• Regression testing (test automation)
• Load/Performance testing

Key Takeaways
In this presentation, you will learn about:

• Techniques that you can employ to test faster without compromising coverage
• The ways in which Process, Technology, and People can come together to accomplish business objectives
• A ‘rare’ Sauce Labs use cases that helped a great deal in the testing process

Bio
Srini Sankar is a quality assurance leader at Aspire Systems, helping organizations move up the Quality value chain from Quality Assurance to Quality Engineering. Driven by a passion to build quality tests that are easy, effective, maintainable, and scalable, he has led digital transformation testing projects successfully for customers ranging from small and medium enterprises to fortune 500 organizations.

DEMO | Sauce Visual

Abstract
Coming soon

Bio
Stan is a Senior Solution Engineer at Sauce Labs, provider of the world’s most comprehensive and trusted continuous testing cloud. He has over 2 decades of enterprise-software experience in the Financial Services, Sports, Marketing/Adtech, CICD, and SaaS Analytics spaces, and is grateful for the opportunity to work with potential clients of Sauce Labs and ensure that the solution they get is the one that they need. Stan has recently completed his novel “Break Point.”

Embrace Your Flakey Tests

Abstract
Ignoring your flakey tests will only compromise your agile team’s commitment to quality, but also let a far too normalized problem persist in our industry – your team’s app and/or framework architecture. That’s right! When your test keeps on failing, embrace your flakey tests. Teams that ignore flakey tests will see them through production and release to customers.

As a team, we need to look into flakiness insights to work on making the app more reliable and testable. 100 test automation is never the end goal for software quality advocates. We know that flakey tests in our team’s build can make a team not to trust the tests even if they might be reliable.

Your tests should be treated with the same care as the application code. We really need to change our perspective and start thinking about what our flakey tests are trying to tell us. In this talk, I will teach you how to embrace your flakey tests to identify what tests you should automate, exercises to enhance quality-processes across your org, and how you can ultimately reduce flakiness as an agile team.

Key Takeaways:

• Identify what tests should be automated
• Learn why automation is a collaborative exercise and should be owned by the entire team
• Get tips on how to reduce flakiness

Bio
Suman Bala is a QA advocate with a passion for improvement in quality processes and is a strong believer in Test Automation. She has honed her capabilities in coaching, mentoring, and team leading, as well as more strategic and technical demands associated with testing. She is striving to instill the idea that quality is everyone’s responsibility as opposed to merely laying it at the feet of QA.

Automating Unified Logging Verification

Abstract
What is the easiest way for QA engineers to gain insight into network requests? The best practice for capturing telemetry from your app for debugging and performance analysis is to use the unified logging system.

When debugging problems in your app, it’s helpful to record the exact sequence of events that occurred, along with supplemental data about those events. Log messages provide a continuous record of your app’s runtime behavior, and make it easier to identify problems that can’t be caught easily using other techniques.

Svetlana Grinevich’s team found a solution that allows them to test the unified logging system and report on logging schema changes. The solution they chose for the task is to enable the Extended Debugging Sauce Labs feature in their Automation tests, which allows them to collect the console logs generated during testing for use in debugging evaluation.

After receiving networking requests and their responses, they parse the traffic logs to filter the requests they want to verify. The next step is to verify request/response layout and parameters values. This solution allowed the team to automate the unified logging verification: cover with the auto tests the full unified logging system, integrate the unified logging tests into the Automation framework.

Key Takeaways:

• How well structured logs can fuel business growth
• The unified logging system as best practice for capturing telemetry from your app for debugging and performance analysis
• A smart solution to test the unified logging system and report on logging schema changes
• Covering with the auto tests the full unified logging system

Bio
As a Lead QA Engineer for Ask Media Group, Svetlana Grinevich’s career includes leadership experience in managing with an emphasis on quality control and software testing, including automated testing, process re-engineering and organizational change management. She has extensive experience as a practitioner in managing test delivery, driving testing and project management transformation, delivering process improvements, driving production stability and managing growth and improvements using data and metrics. Prior to Ask Media Group, I was a QA Manager for Sigmacubed and Teqniksoft. She started her career as a developer at Belgiprozem Project institute and then moved to test automation and test management for several small IT companies. Svetlana has a Masters’ Degree in Computer Programming from the University of Belarus, and Agile Project Management (APMG-International) certification, Agile team facilitation (ICAgile) certification, ICAgile Certified Professional-Agile Testing (ICAgile) certification.

[WORKSHOP] Crafting a Test Framework

Abstract
If you have ever maintained a Selenium test suite, you know that the most expensive piece is dealing with the maintenance costs, not the creation or execution costs. There are straightforward ways to leverage your framework to minimize flakiness and make it easier to update your test code only when needed. We’ll walk through testing a sample real-world application focusing on how each of the components work together.

Outline/Structure

• Writing good tests
• Using Test Data
• Working with Page Objects
• Managing Synchronization
• Encapsulating Objects
• Executing Tests at Scale

Key Takeaways

• What to prioritize when developing test tooling
• How different framework components work together

Bio
Titus Fortner is a core contributor to the Selenium project and the maintainer of the Ruby bindings. He spends a significant amount of time writing open source testing software built on top of Selenium. He is the project lead for Watir and is active in supporting these projects on Stack Overflow, message boards and in the Selenium Slack and irc. Titus has implemented automated tests at five different companies and currently works at Sauce Labs as a Solution Architect, working with the community to facilitate testing best practices.

Intelligent and Optimized Testing Techniques

Abstract
Despite the development teams’ significant efforts to embrace agile development—efforts that included investments in CI/CD processes and orchestration tools, streamlining code management, shifting testing left, and automation—the FannieMae organization continually ran into roadblocks on account of its inability to execute tests within the shorter time frames needed to support an agile development process.The key pillar to success for above is automation. High level of automation is great but if not optimized it can lead to decrease in release cycle velocity due to longer execution cycles and refactoring efforts. There also needs to be better visibility into test coverage and ability to react to changes and validate them quickly.

The Fannie Mae Test Engineering team found a solution. They built robust frameworks and practices around model-based testing for optimization, quality intelligence dashboard for coverage and quality index, responsive visual validation and parallelization and dynamic zero-touch test execution based on incoming code changes using ML. As a result of Fannie Mae’s successes adopting advanced testing practices and tooling (TDD, BDD, model-based testing, build/release quality intelligence, shift-left performance engineering, Chaos Engineering, etc.) and moving teams to a highly scalable test execution platform, delivery teams have been able to deliver more value to Fannie Mae customers, more frequently, with much higher quality.

Key Takeaways:
Attendees will learn how to improve automation efficacy and overall code coverage by building intelligence into your testing process.

• Spend less time in maintaining test framework across teams
• Dynamic selective tests automation
• Faster feedback
• Capturing coverage across different stages

Bio
Tosha Joshi currently works as a senior software engineer with FannieMae on the Enterprise Tools and Test Engineering team. In her 14 years of experience in the industry, she has helped teams with building java applications, business rules using drools, front end (UI) and back-end (API/Data validation) testing. Tosha has a masters’ degree in Wireless Communications Systems and is the mother of two kids, a 3-year-old and a 5-year-old. She enjoys baking, painting and spending quality time with her family.

Selenium: The Weird Parts

Abstract
Selenium has long been one of the go-to tools for many QA engineers. Conceptually, it’s pretty straightforward; launch a browser, find elements, interact with elements, rinse, repeat and then close the browser. For the most part, you can get by with this basic level of understanding. However, this really doesn’t do Selenium justice. Selenium has much more to offer and you may need to dig a bit deeper to handle some more complex challenges.

In this session, Troy Walsh will explore some of the more obscure Selenium features. He will cover things like waits, the difference between different types of finds, running custom JavaScript, driver configurations and more. By the end of his presentation, those newer to Selenium will see how much more it has to offer (and hopefully old pros will have learned an extra trick or two).

Key Takeaways:

• See a bunch of weird stuff you can do with Selenium
• Dive into some of the lesser known features and limitations for specific browsers
• Learn how waits and searches really work and why you need to care
• Explore how event firing works and how it can greatly improve your logging

Bio
Troy Walsh is the national quality engineering Practice Lead and a DevOps lead for Magenic Technologies. He started his career in DevOps as a Release developer, creating custom build, deployment, and installation solutions. He later transitioned to consulting where he developed a love for test automation. Troy is a frequent blogger, speaker and open-source contributor (SeleniumAxeDotnet, MAQS, appium-dotnet-driver and more) with a passion for test automation and DevOps.

Intelligent and Optimized Testing Techniques

Abstract
Despite the development teams’ significant efforts to embrace agile development—efforts that included investments in CI/CD processes and orchestration tools, streamlining code management, shifting testing left, and automation—the FannieMae organization continually ran into roadblocks on account of its inability to execute tests within the shorter time frames needed to support an agile development process.The key pillar to success for above is automation. High level of automation is great but if not optimized it can lead to decrease in release cycle velocity due to longer execution cycles and refactoring efforts. There also needs to be better visibility into test coverage and ability to react to changes and validate them quickly.

The Fannie Mae Test Engineering team found a solution. They built robust frameworks and practices around model-based testing for optimization, quality intelligence dashboard for coverage and quality index, responsive visual validation and parallelization and dynamic zero-touch test execution based on incoming code changes using ML. As a result of Fannie Mae’s successes adopting advanced testing practices and tooling (TDD, BDD, model-based testing, build/release quality intelligence, shift-left performance engineering, Chaos Engineering, etc.) and moving teams to a highly scalable test execution platform, delivery teams have been able to deliver more value to Fannie Mae customers, more frequently, with much higher quality.

Key Takeaways:
Attendees will learn how to improve automation efficacy and overall code coverage by building intelligence into your testing process.

• Spend less time in maintaining test framework across teams
• Dynamic selective tests automation
• Faster feedback
• Capturing coverage across different stages

Bio
Vadym is a Senior Software Development Engineer with more than nine years of experience working on supporting Fannie Mae’s Test Automation and SRE department initiatives. He has extensive experience helping multiple teams to achieve automation in areas including testing, monitoring, and deployment. Currently, Vadym is focused on building different stacks and solutions that are focused on combining modern Cloud resources and AI integration to make his team’s frameworks more agile, faster and intelligent.

Journey to Test Automation: Get Kicked in the A** Then Move On!

Abstract
Traditional organizations who want to move on DevOps don’t necessarily figure out what changes are required to start doing test automation. Because of lack of experience, without internal success stories, teams struggle to initiate the right change and may lose time and money by doing the wrong thing.

An expert group assisting the organization can help, as an eye-opener of course, but it does not solve the entire problem: many attitudes and changes within the dev/qa teams are key factors for a success. Creating a safe zone for experimentation, encouraging training and having affirmed support of management, are some of the behaviors we did experiment, and which brought success.

In this duet presentation – the QA lead of the team, and the lead of the expert coaching group – you will discover how this team did the turnaround to move to a mature practice of test automation. In addition, you will learn how a localized success like this one has been leveraged by the rest of the organization.

Key Takeaways:

• Learn where to start if you want to introduce Continuous Testing in your organization
• Get some tips like events, attitude, and success factors for this journey
• Avoid some pitfalls – you already know them, but be sure not to jump anyway

Bio
Valentin Guerlesquin is a Senior Solution Architect at National Bank of Canada. Prior to this role, he was head of Test Automation, Performance Testing and Test Data Management. He has been a software testing professional for more than 10 years. He is one of the co-authors of “The Missing Link,” a novel about Continuous Testing. Valentin has worked in several roles, including test environment management, manual functional testing, mobile, and testing process improvement. He is an ISTQB full advanced and TMMi certified professional. He has trained dozens of his peers in several organizations from telecom, to the aerospace industry, to finance.

[WORKSHOP] Automation Best Practices

Abstract
In this four-hour workshop, you will learn the most important and innovative automation best practices. You will take a bad suite of tests and use best practices to create a suite that can run cross-browser, in massive parallel, through a Continuous Integration pipeline on every commit. You will also learn how to shift-left as you learn how and when it’s appropriate to write lower level tests like API and unit. Furthermore, you will add visual and performance tests where appropriate. All of this is complete with lots of games and challenges and fun.

Outline

• What makes a good automated test
• How to create good page objects
• How to create resilient tests
• How to create automated atomic tests
• How to correctly test login, links, tabs and much more
• How to properly execute your test automation in massive parallel
• How to integrate your automation into a CI pipeline
• How to do automated visual testing
• Front-end performance testing
• Cloud-grid execution

Learning Outcome
By the end of this workshop you will have a deep understanding of how to test a web application by shifting-left and right. You will use multiple types of tests such as functional UI, API, visual, and performance to cover many testing gaps. You will also do this in a CI environment using industry best practices.

Bio
Solutions architect Wim Selles helps customers successfully implement and get the most value out of their investment in Sauce Labs. He loves to answer questions and help solve puzzles for customers—and he wants to make people as enthusiastic about mobile test automation as he is. Wim conducts training, shares best practices, and travels the world (virtually, nowadays) to make this happen. He has two pieces of advice that he often shares with customers. First, create a solid test base that you can rely on. This will give you confidence in your automated testing efforts. Second, Wim recommends that you avoid coding for coding’s sake. Make sure what you’re doing is really adding value.

DEMO I Mobile App Development and Testing Done Right with TestFairy

Abstract
Mobile testing is complex. You need to test your apps across multiple devices in different environments, and account for the varied conditions experienced by real users in the field. This presents a big challenge for the mobile development and QA teams. Adding to that, being remote, by definition, makes it hard for developers to understand what happened on a mobile device before an app crashed or when things didn’t work as expected. Further, the increasingly quality-sensitive users make it imperative for the modern mobile development and testing teams to deliver a flawless mobile experience with every release.

Join Yair Bar-On, CEO at TestFairy (a Sauce Labs company), and Wim Selles, Senior Solutions Architect at Sauce Labs, as they discuss how teams can address these challenges by managing their app distribution, getting powerful insights into user behavior, using efficient bug reporting, and more. Our experts will provide a deep-dive on TestFairy, the mobile quality platform for the enterprise that helps teams release better apps in shorter development cycles.

You will take away how you can:

• Manage your iOS and Android app distribution in a corporate environment
• Streamline your mobile development processes
• Efficiently manage feedback cycles
• Utilize video recordings and bug reports to uncover and fix quality issues faster

Bio
Coming soon

The Need for Speed (in your CI/CD setup)

Abstract
When developing software and maintaining CI/CD and testing pipelines, we are often compelled to increase our test coverage by adding more tests, and therefore improve our apps’ quality. After all, more automation equals better software, right?

There’s a flipside to this equation however, and a point at which we start seeing diminishing returns from each test we add. Taken to extreme, these diminishing returns begin to actively harm our ability to deliver working software.

In this talk we will look at a tale of creating and taming a monster of an all-day build (one that really happened to me once), and cover tips, tricks, and tools to help you avoid that scenario in the future – from obvious suggestions such as adding resources to your build machines, to less obvious ones like removing tests altogether.

Bio
Zan Markan is a developer advocate at CircleCI, on a mission to educate and inspire developers on the topics of CI/CD, DevOps, and software quality. He’s passionate about serverless technologies, mobile development, and developer experience. Outside of work, he enthuses over airplanes, craft beer, and the Oxford comma.