Building Better Teams Through Play

Abstract
As children, we form strong bonds during recess or at play dates. As adults, we lose this sense of companionship and playfulness. Bring it back to your team with targeted fun activities that create a sense of mindfulness, improve skills, and are just downright enjoyable. Team building is the most difficult aspect of leadership – peer or otherwise. One of the best ways to facilitate team building is play!

Jenny Bramble will present a method for team building outside of the norm in play time. She will show how events can be arranged, when to do them, and what the benefits are for play time – including stronger teams that work better together due to their powerful relationships between team members.

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.

Not Your Parents’ Automation – Practical Application of Non-Traditional Automation

Abstract
Most software companies have an automation initiative. Typically, these initiatives focus on “traditional automation,” using a software package to automate existing test cases or user stories. Not that there’s anything wrong with that; often, there is value in that method. However, if we use only this traditional approach, we miss opportunities to exploit the power of automation. Instead of focusing on test cases, what if we consider this: how can automation help me best do my job?

During this session, Paul Grizzaffi will share real-world examples where non-traditional automation (or “automation assist”) provided business value, highlighting cases where the traditional method could not have provided the same level of testing; you will hear High Volume Automated Testing (HiVAT) highlighted as one of these approaches. You will also hear thoughts to keep in mind when implementing automation assist and see examples of creating helpers from tools not traditionally used for automation.

Key Takeaways

• Traditional automation can be valuable, but do not be blinded by the typical approach
• Ways to utilize automation to help you do your job efficiently
• There is more than one way to use your tools

Bio
As a Principal Automation Architect at Magenic, Paul Grizzaffi creates technology solutions for testing, QE, and QA organizations, including automation assessments, implementations, and through activities benefiting the broader testing community. An accomplished keynote speaker and writer, Paul has spoken at national conferences and meetings; he’s a guest lecturer at UT Dallas. When not spending time with his twins, Paul enjoys sharing with and learning from other testing professional.

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.

The Truth About Oracles

Abstract
There’s a tranquil air through the office, but it’s about to be disrupted by the all too common, but often encouraged, flash of red. POP! The red flies through the office catching everyone’s attention. It’s mostly greeted by curiosity, but several people are well on their way to seeing red themselves! “Is there a problem here?”, no, just the power of oracles.

There are numerous reasons a build can fail, but the one I’m going to be focusing on for this talk is failing automated checks. I absolutely love automated checks, they are a powerful force when it comes to delivering valuable software at pace. The speed at which they can provide actionable feedback is invaluable, but that actionable feedback is based on a well-designed oracle. If the term oracle is new to you, think about your assertions, but it’s important to note that oracles and assertions are not the same.

I’m going to share my journey of studying oracles with you, exploring how the identification of your oracle is crucial in the design of your automated checks. How tools should follow your oracle, and how dangerous it can be to design oracles based on your tools. Exploring the different types of oracles, and how understanding them impacts the feedback you gather, and your automation decisions. How costly the time spent understanding the reason your checks failed can be, and how this can be significantly reduced when a clear oracle is identified and the check built around it.

Every single one of you has oracles, utilises them, talks about them and creates them. Being aware of how that happens, what they are, and codifying them into your automated checks, will elevate your checks to new heights.

Key Takeaways

• Describe what oracles are
• Compare and contrast different types of oracles
• Identify the right tooling to codify your oracles
• Communicate the importance of oracles
• Understand where oracles come from
• Understand the importance of naming your checks to identify the oracle

Bio
Richard Bradshaw is an experienced tester, consultant, trainer and generally a friendly guy. He shares his passion for testing through consulting, training and giving presentations on a variety of topics relating to testing. With over 12 years of testing experience, he has a lot of insights in the world of testing and software development.

Richard is currently the BossBoss at the Ministry of Testing, co-creator of the Automation in Testing (AiT) namespace and blogs at https://automationintesting.com.

Making Your Tests Future Proof with SauceBindings

Abstract
Selenium’s recent W3C specification has implications for anyone running tests on Sauce Labs. As browser vendors deprecate JSON support, it is crucial that tests are updated to ensure that they can still interact with newer browser versions. Unfortunately, for many users this means a complete overhaul, as they are required to change their code. And, depending on the language, some of these changes are structured in non-obvious ways.

Join Titus Fortner, Senior Solutions Architect at Sauce Labs, as he introduces a new tool for customers, SauceBindings, to help simplify working with Sauce Labs sessions. Titus will demonstrate how using SauceBindings provides a convenient way to create compliant sessions, rather than users needing to make changes themselves.

Titus will provide an overview of how to use the bindings, and discuss a number of convenient features that will be added in the future. Attendees will leave this session with a new tool that they can use today to easily create future proof sessions on Sauce Labs without a time-intensive setup.

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.

Fighting a Pandemic with Software Quality

Abstract
We are living in unprecedented times. The Coronavirus pandemic has created new challenges for communities all over the world, and software companies are uniquely positioned to help solve many of them. Now more than ever, flawless customer experiences are needed as many rely on digital applications to provide critical services in the new “normal.” How can your testing strategy help ensure that you are reacting quickly to the demand of your users who need help the most?

Join Karen Motyka, Director of Quality Engineering at Quick Base, as she discusses how her organization’s quality strategy has enabled them to meet requirements for clients that are on the front lines of the pandemic. She will discuss her team’s 2-year testing journey, and how it created a strong foundation that has helped prepare the entire engineering organization for significant growth in both the number of customers and applications developed. By laying the groundwork in not just testing practices, but also in the culture of the engineering team, Karen will demonstrate how powerful quality can be in increasing efficiency and collaboration, resulting in the increased confidence that allows Quick Base to serve their customers in this critical time of need.

Bio
Karen Motyka has been in the quality industry for a number of years and in a management role for the past 12 years. She established and manages both a System Quality Team and a Quality Community of Practice at Quick Base. Focus within these groups has been on supporting framework, infrastructure, and tools needs, enabling teams to move more quickly through process and best practice advancement, and up-leveling quality expertise across the organization. She’s passionate about quality (of course), leadership, and team management. She’s received leadership awards from several programs including the Women Unlimited LEAD Program and Dale Carnegie.

Testing Better with Data

Abstract
Five years ago, everyone in the testing industry was talking about why it’s important to automate more. That battle has been won – automation is a requirement for any team that wants to achieve continuous testing. But more organizations are realizing that their aim isn’t necessarily to increase the volume of testing, but instead to find ways to optimize their efforts. They don’t want to test more, but instead better.

This is why data is the new frontier of testing excellence. Having insights into what is working in your testing practice, what needs attention, and how to prioritize improvements is going to be crucial for teams that want to take their continuous testing journey to the next level.

Join Sauce Labs’ Marcus Merrell, Senior Director of Field Services, and Alistair Heys, Senior Product Manager, as they take a deep dive into some of the ways that data can help augment a continuous testing strategy. Using personal experience, along with real world data, Marcus and Alistair will demonstrate how you can use analytic insights to help accelerate the ways in which quality can contribute to larger business goals.

Attendees of this session will learn:

• How analytics can help improve the quality of your tests, without slowing productivity
• The power data can bring to mitigating quality risks for your organization
• How Sauce Labs is helping you understand your test data, including a look into some of the exciting updates to our Analytics platform

Bio
Marcus Merrell has been working in quality engineering for 18 years. He has been using Selenium/WebDriver since 2007 and is a contributor to the Selenium project and the co-chair of the Selenium Conference Organizing Committee. He has released several open source projects for testing and IoT.

As Senior Director of Field Services at Sauce Labs, Marcus leads a team that is well qualified to help customers with their collective expertise in release management, CI/CD, cloud software and container management. He is also experienced in analytics and marketing automation. Marcus frequently speaks at conferences worldwide.

Panel – Ask the Experts

Abstract
Join Sauce Labs experts for an open conversation about continuous testing, open source software, and building an automation program that delivers digital confidence.

Bio
COMING SOON

Sauce Connect On Demand – A Flexible Tunnel Strategy

Abstract
The test automation team at Dell has expanded its offering for their development teams since they started running Sauce Connect on Kubernetes. Morgan Vergara noticed that since they can quickly and easily create tunnels using Kubernetes, they began receiving a lot of ad-hoc tunnel requests. Rather than continuing to respond to these requests manually, they did what any developer would do: they automated it.

In this session, Morgan will describe the current Dell environment as well as their on-demand architecture.

Key Takeaways

• A more thorough understanding of Sauce Connect
• An understanding of Dell’s complex development environment
• A new way to use SauceConnect tunnels in a more complex environment
• The pitfalls we’ve encountered with our tunnel strategy

Bio
Morgan Vergara has been doing software development for 30+ years, most of it at Dell since 1992. They wrote their first line of code (FORTRAN, for the curious), in 1978 and never looked back.

Will a Bot Steal Your Spot in Software Testing?

Abstract
Stephen Hawking, Bill Gates, and Elon Musk have one thing in common (besides wealth): they’re all terrified of the so-called AI apocalypse, a hypothetical scenario where intelligent machines become our overlords and exterminate mankind. Will AI also take over software testing? My answer to this question comes in three parts. In part (A) I will explore the hype around AI to explain why we are even asking this question. In part (B) I will explore how to define (artificial) intelligence to make sure that you understand my answer to this question. In part (C) I will dive deeper into software testing to finally answer this question.

Key Takeaways

• Learn how to interpret the hype around AI
• Learn what (artificial) intelligence means
• Learn what it takes to completely remove the human element from testing

Bio
Ingo Philipp is VP of Operations at UiPath. His responsibilities range from product strategy, product development and product marketing to test management, test conception, test design, and test automation. Before that, he worked as a theoretical astrophysicist in the field of high-energy particle physics and computational fluid dynamics. He holds a Master of Science degree.

Pinterest’s Philosophy of UI Testing

Abstract
At Pinterest we use UI testing as a tool to ensure quality and improve the quality of life for hundreds of developers. In scaling our UI testing, we’ve learned first hand what works and what doesn’t work. Eventually we cemented it into an internal guide for thinking about UI testing. This presentation will share how we think UI tests should be written and when they should not be written.

Key Takeaways

• An understanding of how UI test strategy fragmentation is an inevitable problem if not actively addressed
• How to align testing strategies between platforms (iOS, web, android)
• How to align testing strategies between teams
• How Pinterest scales UI testing

Bio
Ryan Cooke has worked at a series of small startups. At Pinterest, he found a lot of success in helping the Android team scale through a variety of regression testing. He also has taken over the company’s testing strategy. In his spare time, Ryan is also the reigning champion of Super Smash Bros tournaments featuring over 60 employees from a handful of San Francisco Tech Companies.

Debug Your Apps from Anywhere with Sauce Labs Virtual USB

Abstract
Today many organizations across the globe have shifted to a remote workforce. While this move may be temporary for some, it requires testing teams to reevaluate how they are testing their web and mobile apps. Traditionally a developer would have a number of devices on their desk or available from a physical device cart in the office, but testing and debugging an app when you don’t have the affected device readily available is a hassle.

In a live demo of Sauce Labs Virtual USB, we’ll show you how Virtual USB (vUSB) simulates connecting a real device with a USB cable directly to your local machine during a live or automated testing session. With this functionality you can easily interact with a device in the Sauce Labs Real Device Cloud via an integrated development environment like Android Studio, or using browser-based tools like Chrome DevTools.

Key takeaways:

• Get to know the advantages of vUSB with the Sauce Labs Real Device Cloud
• Learn about the preconditions and setup needed for vUSB
• Understand how vUSB works with an automated and a live testing session

Bio
Karla currently works as a Product Manager at Sauce Labs. Prior to that, she worked as a Product Owner at RatePAY, a fintech company, and before had different roles in the Berlin startup scene i.e. at shyftplan, twago, truffls and epubli. With a background in International Business Administration and her self-taught tech skills she steadily moved into digital product management to build innovative, useful software. Karla is a firm believer in agile methods, user centric design and diverse teams. She greatly enjoys sharing knowledge and interacting with audiences, because there is always an opportunity to grow. She was amongst the TOP10 finalists of RAHM 2018, the global LGBT leadership contest, and named as one of the 50 Women in Product in Europe List 2018.

TITLE

Abstract
COMING SOON

Bio
COMING SOON

Is Automated Testing a Waste of Time?

Abstract
It seems that every engineering and QA organization now has an automation initiative to achieve continuous testing. “Test more!” management mandates, as teams move at breakneck pace to increase the volume of automated tests to ensure that they have coverage. However, could a focus on automating tests for the sake of automation lead you down a dangerous path? The fact of the matter is, while the potential benefits are real, there are some instances where automated testing is a waste of time for your teams.

Join Barbara Kiszka, Digital SDLC Practice and Release Lead at Bose, as she shares her insights into how engineering organizations can create meaningful and insightful automation. Drawing from her 10+ years in quality, Barbara will show how analytics and data can give meaning to your testing efforts at scale, and how in some cases less is better. Using the power of data and reporting, she will demonstrate how teams can create actionable feedback loops that can scale as the amount of automation grows. Finally, she will give advice for teams that are getting started, and how to set the appropriate goals that help focus your efforts.

Bio
After working for several decades as a software engineer, Barbara figured out it was more fun to torture software and then complain about it. In other words she joined the QA team. She is currently enhancing Continuous Integration / Continuous Deployment (CI/CD) for Bose’s many ecommerce websites, including advancing the coverage, reliability, and easily actionable results of the QA automation. She harbors a soft spot for robots, dancing, and dancing robots.

1 Codebase, 2 Mobile Platforms: How to test iOS and Android by just writing tests once

Abstract
Developing consistent mobile apps on iOS and Android is difficult enough, but writing automated end to end tests so they run on both platforms without writing them twice is even harder. The limited selectors on mobile make it very difficult to only use one testing code base for both platforms. By using accessibilityId’s with translation keys in the same way as in the app, we use the fastest and least brittle selector on mobile possible, being resistant to tests breaking in case of text changes, allowing to also check the app in all languages without any additional effort.

Using a hybrid framework like React Native or NativeScript with WebdriverIO, François will show how to use utility methods to cleverly encapsulate all of the platform differences as much as possible, so writing tests is efficient, readable and maintainable.

Key takeaways

• Learn how to apply approaches from developing multi-platform apps with just one codebase (as used in NativeScript, React Native and Flutter) to end-to-end test automation
• Get to know how to easily write tests in a way you can have them run on multiple platforms (even at the same time!) by just writing tests once
• Find out which selectors to use for testing multi-platform apps with the least effort possible
• Learn about testing accessibility and internationalization without any additional effort
• Increase maintainability and readability of your automated end-to-end tests

Bio
François Martin fell in love with test automation while studying computer science. He began working as a consultant in test automation engineering at SwissQ and enabled clients to test all stories automated every sprint. In his current project, he introduced Sauce Labs in order to deploy every two weeks at the Swiss Post and came up with a lot of clever ways to reduce platform specific code to a minimum, so the team can work fast and continuously test iOS and Android.

Testing Using Virtual USB on Real Devices

Abstract
Today many organizations across the globe have shifted to a remote workforce. While this move may be temporary for some, it requires testing teams to reevaluate how they are testing their web and mobile apps. Traditionally a developer would have a number of devices on their desk or available from a physical device cart in the office, but testing and debugging an app when you don’t have the affected device readily available is a hassle.

In a live demo of Sauce Labs Virtual USB, we’ll show you how Virtual USB (vUSB) simulates connecting a real device with a USB cable directly to your local machine during a live or automated testing session. With this functionality you can easily interact with a device in the Sauce Labs Real Device Cloud via an integrated development environment like Android Studio, or using browser-based tools like Chrome DevTools.
Bio
Wim Selles is a Senior Solutions Architect for Sauce Labs based in the Netherlands. During the day, he assists customers with solving automation challenges in their organisation. By night, he practices his passion for front-end test automation with Javascript. He likes to create his own node.js modules to help and support automation engineers and is also a contributor to multiple open source projects that involve testing, such as WebdriverIO, Protractor, ng-Apimock and many more.

Wim also has extensive experience using Appium for automating Hybrid and React Native Apps. He enjoys sharing his automation experience as a speaker at conferences like AppiumConf in London and SeleniunConf India, on his blog and during meetups and webinars.

Orchestrate Your Parallel Testing to Be a Symphony with TestNG

Abstract
When it comes to running parallel tests against the Selenium grid or Sauce Labs VMs, you don’t have to think about coordinating your resources (as much). But what if your resources are limited and you’re constrained by the number of devices of a specific OS/Browser version and you still want to run your tests in parallel? Is it still possible? This presentation will go into the depths of parallel testing with TestNG and provide you with tips and tricks on how to manage/coordinate your parallel executions.

Key Takeaways

• The do’s and don’ts of parallel testing
• An understanding of the strengths of TestNG (e.g. Listeners/Interceptors/Custom Annotations)
• Helpful tips for debugging

Bio
As QA Technical Architect with over 10 years of experience in the field of automated testing, Sergio Neves Barros has worked on automating technologies such as HTML 5, Canvas, Flash, native apps and REST APIs. He has contributed to the Appium project to expand its capabilities of testing with Safari on physical iOS devices. Throughout his career, he custom built many frameworks based on business needs and mentored others on the best practices of building/maintaining their own framework.

Panel – Ask the Experts

Abstract
Join Sauce Labs experts for an open conversation about continuous testing, open source software, and building an automation program that delivers digital confidence.

Bio
Sarah Petrie is a Senior Solution Engineer at Sauce Labs where she works with prospective, new and existing customers to adapt their tests and frameworks and enhance their parallel and cross-browser testing capabilities. Throughout her career at companies such as HP and Cherwell, Sarah has partnered with organizations to modernize IT in both development and operations. She has experience in an assortment of IT Management areas including DevOps, QA, Business Service Management, and IT Service Management bridging a variety of technology stacks and bringing a uniquely big picture perspective to any technical conversation.

Designing a Unified Developer Framework for Functional and Performance Testing

Abstract
Is the high cost of maintaining separate automated functional and performance tests from a select pool of experts vs. from any developer within your organization hurting your bottom line to quality, productivity, and speed? Would you like the opportunity to decrease the overlap of creating and maintaining these scripts along with its associated infrastructure?

Paychex is extending its TAF (Tool Agnostic Framework) from a DSL (Domain Specific Language) script creation approach to a Python coding script creation; this will be done by providing TAF libraries to developers. Paychex will also continue to co-design its new Test Services framework that will provide both functional and performance testing within one solidified platform. This initially provides better Single User Performance (SUP) testing which sets the stage for ideal load creation. This session will share TAF’s current framework that supports over 70K executions per day as well as the early design challenges of creating the new Test Services framework. All of this is designed to directly feed our CD (Continuous Delivering) initiatives.

Key Takeaways

• Business drivers for having both Keyword Driven and Python automated test scripts
• Design decisions to integrate Keyword and Python architectures
• Functional tests to gain early insight into application performance
• Early design decisions to synthesize non-ui and ui performance data

Bio
Danny McKeown has both senior technical and management experience in information technology. As the Senior IT Automation Architect at Paychex, he is instrumental in implementing a secure integration of test automation technologies as part of their continuous delivery solution. Danny is an adjunct lecturer at RIT , sits on the advisory board for IIST, and is a frequent speaker at numerous technology forums.

Learn How the Fannie Mae CRM Team Improved Developer Productivity and Speed to Increase Code Quality for Their Salesforce Application

Abstract
The Fannie Mae CRM team delivers Salesforce solutions interacting with several custom applications and external software integrations, for both internal and external business users.

In the early stages of application development, our developers from 8 different squads, would commit their code development to a Single Master branch. This practice consistently broke builds and delayed execution of Automation tests to the end-to-end testing period. Developers were only able to identify defects and fix them later in the development lifecycle.

As delayed automation testing became a bottleneck, it impacted code quality in production. Our team then set out to answer this question: How can we deliver faster feedback on tests to increase developer productivity?

Towards adopting a shift left approach, our developers transformed the CI/CD process and now execute component tests before they merge new code. This practice helped us identify defects early in the development lifecycle and has maintained a clean pipeline for the development community.

In this session you will learn how to integrate early component tests in the CI/CD process, establish and maintain a myriad of test suites thus increasing software code quality without compromising deadlines.

Bio
Halley Froeb is a Software Development Engineer in Test at Fannie Mae, focusing on developing fast and efficient automation frameworks for Salesforce Testing. Halley is a graduate of Tulane University and has several years’ experience building automation solutions using Sauce Labs. Halley is a certified Salesforce Admin and works to establish innovative practices for automating configuration-based cloud applications.

Learn How the Fannie Mae CRM Team Improved Developer Productivity and Speed to Increase Code Quality for Their Salesforce Application

Abstract
The Fannie Mae CRM team delivers Salesforce solutions interacting with several custom applications and external software integrations, for both internal and external business users.

In the early stages of application development, our developers from 8 different squads, would commit their code development to a Single Master branch. This practice consistently broke builds and delayed execution of Automation tests to the end-to-end testing period. Developers were only able to identify defects and fix them later in the development lifecycle.

As delayed automation testing became a bottleneck, it impacted code quality in production. Our team then set out to answer this question: How can we deliver faster feedback on tests to increase developer productivity?

Towards adopting a shift left approach, our developers transformed the CI/CD process and now execute component tests before they merge new code. This practice helped us identify defects early in the development lifecycle and has maintained a clean pipeline for the development community.

In this session you will learn how to integrate early component tests in the CI/CD process, establish and maintain a myriad of test suites thus increasing software code quality without compromising deadlines.

Bio
Carmerci Jimenez is a Salesforce Certified Administrator and Developer who currently works as a Software Development Engineer in Test at Fannie Mae focusing on developing fast and efficient automation frameworks for Salesforce Testing. She has over two years’ experience developing automation solutions using Sauce Labs with a focus on visual and functional testing implementations. Her passions include continuous integration, promoting innovative testing strategies, and bringing testing practices closer to the development phase.

tour.allThePythonThings()

Abstract
Sauce Labs loves Python. As a first-class language in the Selenium ecosystem, there are several excellent tools for developing browser-based tests with Python. In this talk, we’ll take a tour of these tools based on Pytest, a mainstream test framework in Python, and Robot, a keyword-based test framework. Live demos of these tools will accompany discussion about what makes them helpful for testing with Selenium.

Key Takeaways

• Understand the benefits of using Pytest and Robot Framework
• Learn some helpful libraries and tools for working with browser testing with Python and Sauce Labs
• See some good patterns for designing maintainable browser tests

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 Solutions Architect at Sauce Labs, helping enterprise teams succeed with their test automation. He is based in Toronto, Ontario.

Let Me Tell You a Real Story about our Mobile CI/CD

Abstract
In this session, Moataz Nabil will tell the story behind why Delivery Hero adopted native test frameworks for mobile testing. Since using Espresso and XCUITest is still relatively uncommon for large apps and there are various unique challenges, he will share the Delivery Hero team’s experiences, including:

• A brief architectural overview of the mobile test framework: why it is all native (Swift and Java/Kotlin)
• The advantages and limitations of this choice
• How they are running different test suites and scopes with CI and cloud devices
• Running the tests using different CI/CD pipelines for different apps, different countries and different scope using parameters
• How they make tests reliable: faking address and using features configs

Key Takeaways

• Details of the journey toward our Mobile CI/CD pipeline
• How they are adopting Mobile DevOps and the challenges that we had
• The advantages of using Mobile DevOps
• Why they believe in test automation as one team (shifting the culture)
• Why they are using native mobile test automation tools (Espresso and XCUITest)
• About the tech stack, workflows, and processes in their Mobile CI/CD
• The lessons they learned from our journey and what’s next in our plan (toward AI and Machine Learning in Test Automation)

Bio
Moataz Nabil has 10+ years of IT experience across development and testing roles across industries including agriculture, telecom, healthcare, fashion, and now food delivery. He is currently working as a Senior SDET/Test Automation Engineer at Delivery Hero. He has extensive experience designing test automation frameworks for Web and Mobile applications using a different set of tools and languages and implementing different CI/CD pipeline using different tools.

Building Trust In Your Automation Using Virtual Services

Abstract
For as long as automation teams have been using Selenium, they have struggled with the challenge of managing test data. How do we manage the state our tests require? Even more important, how do we manage the state in between test runs?

Many times, we resort to creating test accounts in specific states or initializing the state via UI during setup. We then revert the state after test run in a teardown or via a post test script. But this adds another cause for failure and, at times, requires manual intervention.

With virtualized services, tests can manage the data they require. Additionally, the test environment no longer needs to rely on unreliable development web services. The result is a less flaky test suite and a purely isolated front-end integration test run.

Mathew will share some of the challenges he’s faced and how he achieved a stable continuous testing pipeline utilizing virtual services.

Key Takeaways

• Learn how to leverage service virtualization to overcome their test data challenges
• Be introduced to virtual service tools, like Wiremock, and service interceptors, like angular in-memory web api.
• Understand how using virtual services provides faster and more consistent test runs.

Bio
Mathew Cano has 15 years of experience in test engineering with over 10 years in building test frameworks and CI/CD pipelines. Over the years, his role has ranged from manual testing, to writing automated tests to mentoring and pairing with developers on writing maintainable and reliable tests, whether unit, functional or integration. Mathew has embraced the continuous testing mindset and is passionate about improving developer efficiency through tooling and automation. He currently works as a Sr. Software Development Engineer in Test at Charles Schwab.

Containerized Testing with Puppeteer

Abstract
In a 2019 developer survey by GitLab, developers were asked where they encountered the most delays in their software development pipeline and testing was identified as the top bottleneck. Similarly, the Web DNA Report from Mozilla Developer Network, shows that testing is one of their biggest pain points. Devs are being tasked to speed things up but often testing is what slows them down. This creates frustrations and challenges and the problem is exacerbated by the various frameworks and tools available.

That’s why Sauce Labs has created Project DevX, which is a new effort to streamline and simplify your testing workflow using Docker and Container technologies. By using a single CLI tool you will be able to run your framework of choice preconfigured with Sauce Labs. This eliminates any setup time and lets you focus on writing tests.

In this session, we’re excited to introduce a new concept for developers that speeds up test execution time, allows you to use the frameworks and languages you know and love, integrates into your existing workflows and is bundled in a container for simplified deployment. Join us to see a live demonstration of this project and an opportunity to provide feedback into our product strategy.

Bio
Kunal is the newest member of the Sauce Labs product team, where he recently joined as Director of Product.. 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.

Automation and Accessibility: Debunking the Myths

Abstract
In a lot of ways, accessibility is talked about and practiced as if it is a hydra dragon. Every time you think you’ve made an improvement, you cut off one head of the accessibility dragon and two heads grow back. In particular, there are a lot of myths out there that you can’t do automation and accessibility in an agile development environment.

A lot of that stems from accessibility being thought of as something you do once, instead of continually, and also that it requires repeated manual effort. The incompatibility with agile is because it is seen as something that has to be done like user acceptance testing or usability testing. And while that’s an important part of accessibility, there is much more you can do to integrate automation and accessibility into your agile processes to produce accessible products.

In this session, Dylan Barrell, CTO at Deque, will disprove these myths and cover best practices for automation and accessibility. Attendees will learn:

• How to interpret design comps to build tests for accessibility
• How to leverage an accessibility automation library, like axe, Deque’s free, automated accessibility browser extension – to catch around 50% of accessibility issues
• Best Practices for how to embed accessibility APIs into your testing practices
• How to automate input device and assistive technology testing
• How to build simple unit or integration tests to serve as a reminder for developers for the manual aspects of accessibility
• How to prioritize and manage accessibility defects systematically in your testing environment

Bio
Dylan is the Chief Product Officer at Deque. He has almost 20 years of experience in technology development, technical sales, product management, product marketing, and corporate development. Dylan founded a startup in 1989 that was acquired. He then went public with OpenText and helped grow revenues to over $400 million. He later led the effort to create a digital center within a Borders store and to begin the transition from purely physical products to digital and physical product mix delivered in a cross channel online and in-store way. In addition to his work experience, Dylan has an MBA from the University of Michigan and a BS from the University of the Witwatersrand. Dylan believes in leading through action to create value for shareholders and the community.

Burstable Testing: How New Manual Testing Methods Compliment Automation Best Practices

Abstract
John Ruberto, QA veteran and Senior Engagement Manager at Testlio, will present the concept of burstability in testing, which emphasizes rapid testing in short timeframes. John will share the story of how a top-10 television network embraced burstable testing within their “shift-left” philosophy to better align with their CI/CD efforts. To make the best use of resources, the TV network combined Sauce Labs automated suites with a global team of on-demand testers. Together, machines and humans worked in parallel to tackle functional, location, and livestream testing.

Bio
Throughout his 20+ years of experience in QA, John Ruberto has taken an engineering approach to building quality into software. He is currently a Senior Engagement Manager at Testlio where he helps clients launch better products, faster. He has previously held positions up to VP of Quality Engineering at First Data, Concur, Intuit, Alcatel, PhoenixBIOS, and Boeing. He holds a BSEE, MSCS, and MBA.

A Practical Example for Using AI to Improve your UI and API Testing

Abstract
Selenium is the most popular framework to create and run web UI tests. UI testing is perceived as easy but is fraught with instability and prone to human error. API testing is known to be more resilient to change but has barriers to adoption due to the deep technical skills required. Both of these testing practices can benefit from test automation. AI can reduce your maintenance time and costs, as well as increase test stability of your automated API and UI tests. Join this session to learn how to make Selenium testing more resilient and apply AI to UI and API testing.

Bio
Rix Groenboom is manager strategic innovations for Parasoft. After an academic career, and before joining Parasoft, he worked for an automated source-code analysis and migration company. He has been working at Parasoft for over 15 years and helps organizations in perfecting their software processes using automated testing solutions. Currently he is responsible for a number of strategic innovations, for example the EU R&D project Testomat. Rix holds a MSc and PhD in Computing Science and published a thesis focusing on the formalization of knowledge domains.

Choosing the Right Deployment Strategy

Abstract
Do you really know how to deploy your applications? Deployment strategies affect everyone, no matter whether we are focused only on a single aspect of the application lifecycle or we are in full control. The way we deploy affects the architecture, testing, monitoring, and many other aspects. And not only that, but we can also say that the architecture, testing, and monitoring affect the way we deploy.

In this session, we’ll discuss different deployment strategies and answer a couple of questions: Is your application stateful or stateless? Does its architecture permit scaling? How do you roll back? How do you scale up and down? Do you need your application to run always? Should you use Kubernetes Deployments instead of, let’s say, StatefulSets? Answers to those questions will not serve much unless we are familiar with some of the most commonly used deployment strategies. Not only will that knowledge help us choose which strategy to pick, but it might even influence the architecture of our applications.

Bio
Viktor Farcic is a Principal Software Delivery Strategist and Developer Advocate at CloudBees, a member of the Continuous Delivery Foundation Ambassadors, Google Developer Experts, and Docker Captain’s groups, and a published author. His big passions are DevOps, Containers, Kubernetes, Microservices, Continuous Integration, Delivery, and Deployment (CI/CD) and Test-Driven Development (TDD). He often speaks at community gatherings and conferences. He published The DevOps Toolkit Series, DevOps Paradox and Test-Driven Java Development., as well as courses in Udemy. His random thoughts and tutorials can be found in his blog TechnologyConversations.com. He is a co-host of DevOps Paradox podcast.

Accelerating Delivery of Business Value through DevOps and ZeroQA

Abstract
COMING SOON

Bio
Greg Wittenbrook is a leader of the Mphasis DevOps Tribe where he works to unlock business value by enabling IT execution through DevSecOps, Quality Engineering, Site Reliability Engineering, Agile, and IT Operating model optimization.

[DEMO] Getting Started with Sauce Visual

Abstract
In this live demo, Ian Flanagan, Senior Solution Engineer at Sauce Labs, will show how to get stared with Sauce Visual.

Bio
Ian Flanagan has been in the computer industry for over 20 years and has worked directly in QA for over 15 years, including experience with manual, automated, desktop web, headless, Visual component testing, mobile, API testing, performance, and load testing. He also has extensive experience in appium and selenium using variety of languages and frameworks including espresso & XCUItest. In addition, he has a deep background in databases, devOps, virtualization, production monitoring, and system administration. Ian is currently a Senior Solution Engineer at Sauce Labs, helping enterprise customers be successful. He is based in Austin, TX.

Containerized Testing with Puppeteer

Abstract
In a 2019 developer survey by GitLab, developers were asked where they encountered the most delays in their software development pipeline and testing was identified as the top bottleneck. Similarly, the Web DNA Report from Mozilla Developer Network, shows that testing is one of their biggest pain points. Devs are being tasked to speed things up but often testing is what slows them down. This creates frustrations and challenges and the problem is exacerbated by the various frameworks and tools available.

That’s why Sauce Labs has created Project DevX, which is a new effort to streamline and simplify your testing workflow using Docker and Container technologies. By using a single CLI tool you will be able to run your framework of choice preconfigured with Sauce Labs. This eliminates any setup time and lets you focus on writing tests.

In this session, we’re excited to introduce a new concept for developers that speeds up test execution time, allows you to use the frameworks and languages you know and love, integrates into your existing workflows and is bundled in a container for simplified deployment. Join us to see a live demonstration of this project and an opportunity to provide feedback into our product strategy.

Bio
COMING SOON