SYNAPSE QA is a community-driven space that aims to help testers believe in themselves and serve as a launchpad to inspire them to transition from dreamers to doers.

The community has many rich voices, ideas & experiences, but they are usually lost somewhere. We aim to provide a platform which connects and finds those voices. We strive to continuously empower the community with innovative ideas that improve how content is published, evaluated and communicated to the audience and the public.

Our mission is to empower testers to believe in themselves and confidently share knowledge.

Synapse QA

In an era where AI and automation are transforming software testing, how do testers stay relevant without losing their core skills?

This panel brings together industry leaders to explore the balance between AI-driven automation and fundamental testing expertise. Discover how to adapt, upskill, and lead in a changing landscape—without compromising the essence of quality assurance. Join us for an insightful discussion on navigating the future of testing with the right blend of leadership, automation, and AI expertise.


AI & Test Automation: Evolving Without Losing Core Testing Skills

Behaviour-Driven Development (BDD) bridges the gap between business, development, and testing teams, ensuring that the software behaves as intended even before coding begins.

**Some key takeaways you can expect are**

*   Drive higher product quality through clear, behavior-focused scenarios
*   Enhance collaboration between testers, developers, and product owners
*   Ensure automation aligns with business goals, reducing defects


Synapse QA Webinar: Behaviour Driven Development: Building the Right Product

One of the biggest reasons UI tests break often is the use of unstable element locators. In this session, I’ll discuss strategies to write more stable element locators, introduce UI-licious - a low-code testing tool - and do exercises to show you how to write stable semantic tests with UI-licious to test user journeys, not HTML.

## Outline

1.  What makes automated UI tests flaky?
2.  Strategies for writing more stable element locators
3.  What is UI-licious? : Test user journeys, not HTML Philosophy
4.  Hello world with UI-licious: We’ll do a short exercise to login to GitHub and cover the basic commands to navigate, fill input fields,
5.  What about icon buttons and images? : We’ll do a short exercise to test icon buttons and images and explain how UI-licious works to target elements based on accessibility attributes.
6.  What about similar elements?
7.  Hinting using I.see: We’ll do a short exercise to explore using the I.see command to hint at the element targeting algorithm.
8.  Scoping using UI.context: We’ll do a short exercise to use UI.context to set the search scope for the element targeting algorithm.
9.  Using Page Object Model in UI-licious: Page Object Model is a good way to manage the complexity of the codebase for a UI test project by creating reusable functions that represent the state and possible interactions with a UI component.
10. We’ll do a short exercise to create a page object model to test a larger website.
11. Fun and Games: Testing 1 to 100 game with UI-licious: We’ll do a short exercise to write an automation script to play a game of clicking numbers randomly positioned in a grid from 1 to 100.
12. Q\&A: Open to any questions from the audience.


Test user journeys, not HTML: Writing stable semantic UI tests with UI-licious

Have you ever experienced a situation where you have created hundreds of scenarios, tested thoroughly and passed the AUT to UAT? During the UAT, someone suddenly caught an obvious high-risk bug they quickly found with a few extra taps. 

You feel embarrassed and anxious at that moment and start questioning your competency. How could you have missed such a crucial obvious bug? How did the other person manage to find it within a few taps? What went wrong despite having hundreds of test cases?

**Was it an act of chance? Luck? Or competency?**

Join me in understanding this situation and how you can harness this super skill by incorporating Serendipity in Testing.

Key Takeaways:

1.  Discover techniques to enhance the probability of encountering a critical bug or a solution through serendipity 
2.  Examine the advantages and disadvantages of linear and non-linear testing, and leverage the strengths of each approach to achieve better testing outcomes
3.  Identify different strategies that can be employed to enhance serendipity during testing.
4.  Discover the benefits of integrating serendipity into the testing process
