Stop over-testing the same functionality and avoid risky under-testing – leverage changes from across the SDLC to “rightsize” testing based on time and risk.

Understanding the importance and the need of API Security and how you start implementing it.

In this session, you'll learn about the importance of mindset needed for best performance in automation testing.

You'll also discover the habits that are important for automation engineers.

Unit testing is fine, but without proper integration testing, especially if you work with external resources like databases and other services, you might not know how your application will actually behave once it has been deployed to the real production environment.

Before Docker, configuring the environment for integration testing was painful – people were using fake database implementations, mocking servers, usually it was not cross-platform as well. However, thanks to Docker, now we can quickly prepare the environment for our tests.

In this talk, I would like to show how you can use Testcontainers ( https://github.com/testcontainers/testcontainers-java ) – a popular OSS JVM testing library that harnesses Docker to easily, reliably, spin up test dependencies.

As a special focus, we want to have a deeper look at the development and the addition of new features to the Testcontainers library in the recent past. But that’s not all, we will also share an outlook at the horizon of the future of Testcontainers and might even get a glimpse at some brand new features that are currently in active development.

Being a tester is like being a pokémon trainer: we want to choose the right pokémon for the job. The problem with doing different types of testing is that we also end up with multiple scripts in different languages and testing tools. We end up choosing a squad of pokémon: one for unit testing, one for automation testing, one for load testing, and so on. Making sure they all work together is a task in itself!

But what if we could just use one? What if we only needed one Mega-evolved pokémon that could fulfill multiple roles? Is it really possible to write a browser automation script and then reuse it for load testing?

In this talk, I will talk about my search for the elusive one pokémon that does multiple jobs, the advantages of hybrid load testing, and how to pick pokémon that make our life as trainers and testers easier.

Software testing is often considered a side activity, almost a “necessary evil”.

With the acceleration of software development lifecycles along with higher dependency on software in business and private environments, software testing is facing new challenges of increased workload.

More and more companies decide to face these challenges with the help of test automation.

This raises new questions: What should we automate? Can we keep the test assets we created over the last decade? Who will develop the tests?

Like with any development, test automation needs a firm foundation made of requirements.

In this session, we will look at some techniques for requirement elicitation related to test automation, and discuss how collaboration within the team can be improved.

It’s 2022, and cross-browser testing (CBT) is as important as ever. Our apps need properly-responsive layouts to handle the myriad of platforms and screens in our digital world. I’ll be straight, though: CBT at scale is a challenge. Just like any facet of testing, it requires risk-based planning and a well-engineered implementation.

In this talk, I’ll share my real experiences with CBT. We’ll cover pros and cons of different strategies for choosing browsers, building versus buying infrastructure, and optimizing execution with visual testing techniques. I’ll share my experiences on aspects like speed, reliability, and maintenance, too. After this talk, you’ll be able to make awesome choices for your modern CBT needs!

Do you know that the same function can become 10 times faster just using another algorithm and changing data structure in some cases can extremely increase performance?

Discover how to use Big O notation for optimizing your tests code to make them faster and effective.

Testing data is a gold mine that is rarely explored when discussing software quality and best development practices. Tens of thousands of tests might be executed in your CI pipelines day by day, generating a massive amount of data for you effortlessly. Right now, this data is lying around without producing you any value, but — what if you could harness this data to accomplish something?

If you used it correctly, you could be able to, for example, detect test flakiness, notify the right people about failures, and much more. All you have to do is capture this data and turn it into insight using an instrumentation layer.

You can add this instrumentation layer on top of the jUnit de-facto standard for test reports. By doing this, you will be able to send traces and metrics to a backend using another standard, OpenTelemetry, and explore that information from there in whatever manner it is helpful for your interest.

In this talk, Mala will share a holistic view of the challenges of traditional software testing in the complex Salesforce testing ecosystem and provide a roadmap for leaders to overcome implementation roadblocks in partnership with R&D teams.

Finally, Mala will demonstrate how an investment of a DevOps solution with a Sauce Labs integration helped her agile team achieve time reduction of up to 50% for overall flow, while doubling release velocity without additional headcount.

If you are a manager looking to scale end-to-end testing coverage and/or wondering how to take a holistic approach to Salesforce test automation, you won’t want to miss this leadership session.

In this talk, front-end web app developers and testers would get to learn the most advanced and little-known features of the Cypress framework.

The presentation would establish the point "why designing the automation right is important but often neglected?"

In this talk, we will explore what accessibility means, why it is important, and what this looks like on both web and mobile applications.

Accessibility takes on many forms, as there are a wide range of humans out there who have different needs and abilities. Technology has made it easier than ever to adapt to all kinds of human needs and uses, however all those needs aren’t always on every developers’ radar.

In this talk, you'll see what tools are already available for accessibility testing, and also delve deeper into the world of adapting for all users, exploring the needs and possibilities that a QA tester should consider when testing an app for usability.

Takeaways:

• Learn how to identify gaps or blindspots you may have in considering what functionality to build into an application
  
• Become more equipped to create diverse, inclusive tests and help your teams engineer higher quality products
  
• Understand the technology and tools available for a11y testing, and what needs exist on the automation front for addressing more accessibility issues for users.
  
• Explore some of the existing a11y automated testing functionality available for web app testing
• Explore our own blindspots when it comes to accessibility testing, and brainstorm about what needs exist
  
• Understand the scope and function of assistive technology available on mobile devices
• Explore a case study where a company with a mobile application does extensive accessibility testing on real devices, and explore what they test, and how better test automation can help them and their customers
  
• Discuss what basic considerations should be included in testing programs to ensure we are meeting all a11y accessibility standards