First Week end Testing participation

Week end testing Participation 

My first time participation in the Week end testing happened last week and there were 2 sessions.

• Configuration Tests on Mobile Devices 
• Scenario Testing  - www.amazon.com

This post is related to Scenario Testing on www.Amazon.com

Ajay explained on Scenario Testing from Lessons Learnt in Software testing as

• The test must be realistic. It should reflect something that customers would actually do.
• The test must be complex, involving several features, in a way that should be challenging to the program.
• It should be easy to tell whether the program passed or failed the test.
• A stakeholder is likely to argue vigorously that the program should be fixed if it fails this test.

As Ajay mentioned in the transcript, almost all of us were first timers and the questions regarding the context were very less.

The exercise helped in 

• Thinking about identify various means by which a Customer will operate the website. A possible technique is to identify the possible list of features available in the site by various means requirements docs(may not be latest), brainstorming with the stakeholders, Development Team, Comparable Products etc

Whether a Function Interaction matrix  can help in identifying scenarios across the interaction points ??

Learning

1. Understand what is important in E2E Scenario testing 
2. Time management  - Understand the context, Test, Prepare the Report
3. Most of us tested in similar way except Ajay that resulted in a defect.  Have to understand the subtle difference between functional & scenario testing
4. Focus & De-focus - to avoid getting distracted
5. ...