Worqference – Ajay Balamurugadas & Balaji Ponnada – Systematic Product Modelling

4-5-6 March, 2022


Learn to apply techniques and approaches to model any product under test
Atomic Workshop by Ajay Balamurugadas and Balaji Ponnada at Worqference 2022

Who should attend?

Why one should attend ?

Session Details

Atomic Workshop | 90 Minutes | Followed by 15 Minutes Q&A
23rd August, 2020 | Sunday | Online Even
4:00 PM IST to 8:00 PM IST
6:30 PM SGT to 10:30 PM SGT

A complex product and very little time – you are called in to test it. How do you learn the product and structure your exploration to yield deliverables? Are you confident that you have covered every component or interaction? Applicable for any product/service, stand up for scrutiny and impress all.

There are several screens with multiple sections and each section is related to some other section across multiple screens. You are called in to test the product and after a few minutes of exploration, you discover that your mind is exploding with the combinations possible. How do you explore and document in a way that it is not just understandable to you but to every stakeholder? Which approach will help you cover the multiple interactions and also focus on the individual components right up to the field level?

These techniques are recommended for teams looking to strengthen their test design, improve overall system understanding and be ‘test ready’ for every change that is made to the product.


  • Introduction – establish objectives for the session 
  • Kipling’s method around modelling 
  • Product coverage outline 
  • Modelling on couple of applications
  • Least tapped resources for test idea generation (Website, Demo Videos, Help Guides, Customer Forums, Reviews), Exercises 
  • Q&A

Workshop Instructors


Senior Director QE

Ajay Balamurugadas, goes by the handle ‘ajay184f’ in the testing community and is continuously re-inventing his testing methodology. He co-founded Weekend Testing – a worldwide movement for skilled testing, authored multiple books available at bit.ly/booksaj and
bit.ly/ajleanpub. His friends associate the terms – ‘Change Agent, Idea Man, Motivational’ to him. He tweets under @ajay184f and loves to have long conversations on software testing and life in general. He is currently working at GSPANN Technologies, Inc. as Senior
Director – QE. When not testing, he spends time with his wife and two children.


AVP Testing

Balaji Ponnada, has about 15 years experience in Software testing, a context driven tester and worked extensively at different phases of test cycle – planning to execution & reporting for various clients. Comes with rich pre-sales experience, understanding client pain points and engineering a solution to address pain points, Conducting proof of concepts. Expert consultant in reviewing client processes via stakeholder interviews to address current testing problems and defining future state of testing to meet business objectives. Extensive experience working with K-12 education systems and leading LMS Moodle, Edmodo and Blackboard.

He also heads IoT research center, Responsible for research, Collateral creation and business development into IoT projects, Defining and implementing Test strategies for IoT systems. Research and collaboration into MQTT, Bluetooth, BLE, Zigbee protocol level testing and implemented devices.

for this Workshop and 14 others at Worqference 2022

Worqference also has 14 More such Workshops. See below.

Exploratory Testing is one of the most important skills testers should have. Despite fully knowing the significance of ET, it is often treated as an after-thought or simply as a type of testing one could do on top of everything else that had to be done. Simply relying on automated checks and testing acceptance criteria does not find us the information that stakeholders can use to make decisions about quality/risk. Often times testers struggle with making Exploratory Testing as a part of their test strategy or let’s say in Agile/DevOps teams they find it hard to fit ET in their testing activities. 

It is crucial to involve exploratory testing as early as possible in SDLC. And it is very much possible to do so.  Session Based Test Management is an approach to manage and structure Exploratory Testing. With SBTM approach testers can better plat ET and also evaluate how their testing efforts are organized. 


  • Steering clear of a mistaken notion of Exploratory Testing 
  • Understanding Session Based Testing and how it is done 
  • SBTM in action with practical examples 
  • Practicing SBT with hands-on exercise (creating charters, performing sessions) 
  • Overview of tools that support SBTM 
  • Review of the student work and feedback (selected few)

Visit Speaker Page

The responsibility for product quality often falls on software testers. Yet, software testers are often divorced or even excluded from conversations around the cheapest and easiest way to inject quality into the product and the entire software development life cycle, right from the beginning: robust unit test frameworks.

Sure, unit tests are the job of developers, and some developers and companies won’t even think about writing unit tests. So why should software testers know and be able to work with unit tests? As advocates for overall product quality, being able to analyze, discuss, and improve or ask for improvements in unit tests is one of the cheapest ways to advocate for product quality at the earliest stages in the software development process.

In this workshop, using an open source python repository, testers will learn:

  1. Why unit tests are important, and the typical problems in many unit-test frameworks
  2. How to find the unit tests in a code repository
  3. How to understand what unit testing library is used, by reading the code
  4. The main words to look for in unit tests in any language (x-unit testing frameworks) and what those words mean
  5. How to figure out what a unit test is doing
  6. The best questions to ask developers about unit tests
  7.  The best tests to add to the unit test framework so you don’t need to repeat efforts manually or in front-end automation
  8. How to lead the conversation when there is no or poor unit testing in your product

By the end of this hands-on workshop, testers will understand how to read source code, determine what tests are in the code, and work with developers and dev managers to help develop more robust unit testing frameworks and decrease manual and front-end test automation needs.

Visit Speaker Page

Automation is one of the challenges which Testers are facing every day and still most of us are unable to build a reliable script and create an environment where we can easily debug and resolve the issue, capture screenshots/videos of the entire flow, control the execution speed, store execution reports, handle flaky cases, and this list goes on and on.

We invest a lot of time to build the perfect framework as per our needs and we still end up scrapping it after a couple of years. So, I started looking for a tool that can take care of all the ad-hoc tasks and I can solely focus on adding test cases to my suite, and soon I stumbled upon Cypress.

Cypress is a tool that helps us to write Unit, Integration, and End to End test cases for UI and API. So it can be used by a Developer or a Tester.

Cypress is bundled with features like

  • Time Travel
  • Debug Capabilities
  • Automation Waiting
  • Spy/Stub API requests
  • Inbuilt screenshot and video capturing capabilities
  • Supporting cross-browser execution
  • Controlling browser resolution and much more 🙂

In this workshop, we will explore some of the Cypress features which are required to write stable automation scripts. We will be using Javascript as our base language and Mocha for writing test cases.


  • Creating test cases to interact with different UI elements and make API calls
  • Configuring Properties and Environment variables
  • Executing scripts on multiple environments
  • Spying/Stubbing XHR requests
  • Externalizing test data using fixtures
  • Integrating execution reports with Cypress Dashboard
  • Running scripts on multiple browsers

Visit Speaker Page

Have you heard of Contract Testing? Are you currently working on a project involving multiple data providers? Do you want to make sure that consumers and data providers can catch broken changes earlier on in your pipeline? If the answer to these questions is yes, then this workshop is for you! In this workshop, I’ll explain what contract testing is, how it’s different from other types of testing, its features and benefits. No workshop is complete without a live demonstration so I’ll also be walking you through how to setup both consumer and provider contract testing using Pact JS with Jest.


  • Problem Statement
  • Issues with unit testing and/or traditional integration testing
  • What is Contract Testing?
  • Features and Benefits of Contract Testing 
  • When not to use Contract Testing?
  • Walkthrough of example Rest API to test
  • Installation and pre-requisites overview
  • How to set up Consumer Contract Testing
  • Introduction to Pact Broker
  • Uploading the contract to the Pact Broker
  • How to setup Provider Contract Testing

Visit Speaker Page


Digital Accessibility is no longer an afterthought. It has become an important facet in software design and engineering, given the rapid digital transformation that the world is witnessing. Also, it is no longer limited to just a specific accessibility group that is responsible in enabling digital inclusion. Right from business teams to developers to functional testers, everyone needs to be sensitized on what is accessibility and how to make it a reality in products built for end user consumption. Industry standards are easily available today for global consumption that define how to embrace digital accessibility in mobile and non-mobile worlds. This workshop will give the right first view into the world of accessibility where you will go back with an understanding of the varied guidelines of WCAG (one the leading global accessibility standards) along with test techniques, tools and practices.


Introduction: 20 mins

  • What is and Why Accessibility?
  • Accessibility in Today’s Context
  • Types of Disabilities

Guidelines: 40 mins

  • WCAG2.0/2.1 Guidelines with Examples (2.2. is also around the corner)

QE: 20 mins

  • Testing Process
  • Assistive Tools
  • Scope for Automation
  • VPAT


Visit Speakers’ Page

You might have heard me talk a lot about how waits can improve the reliability of your Selenium automated tests. But maybe you did not clearly envision how you can apply them in your own tests. Or what specific wait methods can be created for specific page interactions. In this workshop I will go over lots of examples where we will update existing non-wait tests to use waits. We will see what makes sense to wait for in each example, and how we can create the best wait method to handle each scenario.

Visit Speaker Page

Whether you are a seasoned manager, a senior tester tasked with leading a team or a project, a prodigy that wants to get their career rolling, or simply someone who is serious about their professional development, you want to create a career that you are passionate about.

As your expertise grows, you are assigned a higher level of responsibility, and you are expected to demonstrate leadership in your daily work – in one way or another. That could be influencing, defining strategy, coaching or leading the team (whether your direct reports or your peers) in a new direction.

Also, your professional community is looking up to you – there are expectations to see you as a role model, a thought leader, a person who can share knowledge and teach others in the expertise they possess.

These new levels of responsibility sometimes leave you with questions: Am I doing the right thing? Am I really the expert people think I am? Do I possess the level of knowledge and skills that’s necessary to make right decisions? Am I applying my best in where I am or should I put my efforts elsewhere to achieve the career satisfaction I want and deserve?

This workshop is designed to help you identify your REAL strengths, take a close look at your leadership style, and equip you with the tools that will enable you to achieve your next career goals.


  • Discovering personal leadership style and traits
  • Identify career-related strategies for career progression or transition
  • Interaction to address career-related queries and challenges

Visit Speaker Page

Overview & Purpose:

The key goal of any bug reporter is to provide high-quality information, well written, to help stakeholders make wise decisions about which bugs to fix. Although most testers find and report bugs in their day-to-day work yet only a few are very good at it. This workshop is designed to help you be a Good Bug Advocate.

Principles Driving This Workshop:

  1. Bug Advocacy is a persuasive skill that requires thorough investigation, analysis, and clear reporting.
  2. Bug Investigation and Reporting Skills can be me made systematic and faster using suitable resources, oracles, heuristics, and tools.
  3. Bug Advocacy is one of the Core Foundational Skills for any tester who want to be good in this field.

Why someone should care about this Workshop:

  1. Become an influential tester of your project.
  2. Learn how to effectively convey risks and meaningful information using Clear & Credible Bug Reports.
  3. Learn how to use Tools, Oracles, Cheat sheets, & Other Resources to be good at advocating for bugs & quality.

Overview of Topics to be Covered:

  1. Basic Concepts: Explore “quality” and “bugs” in detail. Anatomy of a Bug Report.
  2. Persuasive Bug Reporting: Making People Want to Fix the Bug: Creating reports that clearly communicate bugs in their honest light so that decision-makers can make a quick wellinformed decision.
  3. The Content, Clarity, and Credibility of Good Bug Reports: How to structure reports in more useful and credible way for better decision-making by others.
  4. Tools & Tips: Tools & Tips to be more efficient at bug reporting.

Targeted Audience:

  1. Testers: Who deal with finding and reporting bugs in their day-to-day work.
  2. Leads & Managers: Who want to train their team to be good at bug advocacy.
  3. Developers: Who want to save their day-to-day time by guiding testers to provide them with clear and concise bug reports

Topic Wise Breakdown:

  1. Exercise to Understand Current Level of Attendees.
  2. Understanding key concepts (such as software error, quality, and the bug processing workflow).
  3. Scope of bug reporting (what to report as bugs, and what information to include).
  4. Reporting as per target stakeholders (Devs, Managers, etc.).
  5. Credible Bug reporting. (With Exercise).
  6. Bug investigation Skills (With Exercise).
  7. Structuring of well-written bug reports.
  8. Tools to help with Bug Reporting.

Visit Speaker Page