Session based testing

We had again very nice overview of Session Based Testing and tools: Session Tester and RapidReporter. Tools were quite simple to use and light weight. Basically those are timer, documentation and presentation helpers. Metrics and documentation during testing can be formed to html documentation.

We start our final dojo by creating smaller testing groups. Each group got own device either computer or Android tablet/phone. Groups with computer should test University of Turku web site and other groups test Fuugo application. I start in Fuugo testing group. At the start Fuugo testing groups start to explore application how it works etc. After 15 minutes all know what to test and quite well how. We decided session length should be 45 minutes. My group decides to test main view search functionality. We tried everything what comes to mind how to break searching functionality without finding any error. We keep documentation on paper of every testing and added comment of our tests. Suddenly our instructor says we had to change testing group and leave our documentation on the desk. Now we got open web site and documentation written by someone else. That was hard find out what they have been done. We check some points what they have been done so we understand better their documentation. We didn't expect that other groups start to read our documentation. Hopefully other group understands our writings. Web site was still buggy as earlier dojos. Bugs were again localization problems and some dead links. After session we change again back to original positions and start to continue where we leave. Other group has not found any error either. Some new test aspects have been written in documentation. After this session we didn't find any errors at all from main view search functionality. I admit time boxing help to focus to relevant things in testing.