Testing is like fishing – fishing for bugs. To ensure ‘all’ the fishes are caught and that the final product is indeed robust, it is necessary to have robust fish-net that can catch ‘all’ the fishes.
This implies that test cases do cover the entire software. How do we prove this? How can we ensure that this can be done in the given time constraints?
The typical test design techniques like equivalence partitioning, boundary value analysis, state machine are not sufficient to meet these objectives.

About the workshop
This workshop discusses a unique approach whose focus is to construct a hypothesis of potential defects and then design the ‘fish-net’ that is indeed robust. Designing test cases based on “Hypothesis-based testing” is about coming up with minimal yet effective test cases that examine the complete behavior of the software ensuring the delivered software is indeed robust.

Founder and CEO of STAG Software Private Limited. Passionate about excellence, his mission is to discover methods to build clean software.
Enthusiastic about sharing knowledge, he conducts workshops and speaks in key forums. At STAG he is deeply involved in the Science and Engineering of Testing to develop methods and tools to engineer effective tests.
He is an alumnus of IIT Chicago and Anna University, India with over 23 years of work experience. He was awarded the “Thought leadership award” in the Test2008 conference for his “thinking and questioning oriented approach to test engineering”.

Who should attend?
Test designer, lead/manager.
It is expected that you have a good understanding of test engineering. It is even more important to ensure that you have open mind and be able to unlearn.

Topics
This is not a typical workshop that teaches jargons of testing.

* Clear expectation articulation–Defining ‘what is robust’. Ensuring expectations are articulated objectively.
* Defect hypothesis – What potential defects may exist in the software?
* Staged detection – Defining quality levels and associating focused test types with these levels. * Design approach – Based on Behavior-Stimuli approach of STEM™ 2.0
* Measuring coverage – Fault coverage in addition to requirement coverage
* Automation advantage – How does this approach aid in automation?
* Test documentation – Writing short, yet effective test documentation

Learning model
The learning model is an application-driven model wherein a real-life product is used to illustrate the concepts.  Additionally, participants are expected to solve problems applying the concepts taught.

About STEM™ 2.0
STEM™ 2.0 (STAG Test Engineering Method) is a scientific and disciplined way  to produce clean software. It is a goal based method that consists of clear steps organized by phases and disciplines to achieve the goal. A core set of scientific concepts powers each step in the various disciplines of STEM ensuring that each step is done in a scientific manner.

Venue & Registration details