Date: April 7th, 2012 11:00 a.m. – 01:00 p.m. Pacific
Michael Larsen, Molnár Zoltán, Robert Donahue, Lanessa Hunter, Pushpa Raj, Eugenia Yakhnin, Ranjit Shringarpure, Ashwin Maharaj, Rahul Vig, Victor Mclean
We focused today on looking at a site that offers to teach people how to program,
We set the session up today as a good old fashioned bug hunt…. with a twist. As an added bonus, we approached the application from the perspective of doing scenario based testing.
Scenario testing is a software testing activity that uses scenarios: hypothetical stories to help the tester work through a complex problem or test system. The ideal scenario test is a credible, complex, compelling or motivating story the outcome of which is easy to evaluate. These tests are usually different from test cases in that test cases are single steps whereas scenarios cover a number of steps.
We used the following resources to help explain the idea and rationale behind scenario based testing.
Each of the testers were asked to go and spend some time on CodeCademy, work through the first example exercise, and then report back as to the following:
1. Describe the scenario you were able to construct.
2. Explain issues you encountered along the way.
3. If you found anything of note, share them in the chat transcript.
There were a number of interesting issues that were found, one of them being someone who entered in an Irish Name of “Danny O’Brien”. The very first screen had a problem with this, and couldn’t accept that value. This is an example of using a scenario (playing with not as common names) we were able to find a deficiency in the program. Other issues were also discovered using a similar technique, where instead of just looking at test cases, the tester created and processed a coherent story so that they could look at a broad range of criteria to determine if the program was doing what it should.
Full chat transcript is here.