Analyzing and understanding a story for creating the test objective and scenarios is not an easy task. This requires a lot of effort for identifying the exploratory scenarios which has to be covered in all aspects. Even though the best possible story cannot explain the hidden challenges to the QA or developer the challenges and scenarios it can override and fish upon the application. To explain and dig more into the scenarios diagrams and figures modelling is a great tool for any QA to understand the flows and challenges involved . Similar to the UML diagrams we have used a new technique to understand the complete flow of complex stories and the dependencies of the same on various interfaces.
What we did?
We tried figuring out the best possible method for documenting the scenarios and linking the previous and future scenarios to the plan. The method adopted is to create scenario modelling diagrams to create and understand the flows, complexities and dependencies of the story. These diagrams helped us deciding the best methodology for testing, deciding the best combination of test cases, the flow for testing, coverage addressed, etc,..
Test Scenario Diagram
While designing the diagram we made sure each symbol and box had a meaning in the test case flow and design. The colors even represent whether a test case has multiple steps, single step or a scenario within another scenario.
Advantages.
This really helped us in the TDD approach in agile. We were able to model the dependencies in a much better way. This helped us in understanding the depth of coverage to a greater extend. We were able to have a three dimensional approach to the test scenarios for stories.
Soon we will be publishing a paper on this approach.
No comments:
Post a Comment