EWT08 – A wiki in your pocket

EWT08 – A wiki in your pocket

Date: 6th March 2010
Time: 15:00 – 17:30 GMT

Product Tested: Wiki on a stick

Mission:
Use the SFDPOT heuristics to test Wiki on a Stick.
- SF DePOT (Structure, Function, Data, Platform, Operations, and Time)
- http://www.satisfice.com/articles/sfdpo.shtml
- http://www.developsense.com/articles/2005-10-ElementalModels.pdf

Report your bugs and test reports to bug repository (http://bugrepository.com/) under the Project EWT08 until 16.30 GMT.

Testers: Anne-Marie Charrett, Tony Bruce, Maik Nogens, Jeroen Rosink, Vijay Kalkundri, Daniele Castellitto (project manager from Wiki on a Stick), Michael Bolton, Ajay Balamurugadas, Anna Baik, Markus Gärtner

Anna Baik and Markus Gärtner facilitated the discussion. Each tester was asked about their experiences.

Markus Gärtner started the discussion. Markus explained that organizing the session report in parallel did not leave much time for him to test. In the end he found out that the two bugs he thought he had found, were no bugs at all. He played around a bit with the two browsers he uses frequently, FireFox and Opera, opening and saving pages cross-wise. After testing around the issue, he found out that the problem sat in front of the computer.

Jeroen Rosink continued the discussion. He had tested on two operating systems. The application itself was not very intuitive to him. That’s why he toured through the application. The surprising element for Jeroen was that the application was in fact the web-page included in the download. Installation was therefore really easy. Jeroen also managed to work with an USB-stick to test the application. He consulted the documentation to get to know there is a way for synchronization when the installation went properly. Jeroen found it hard to concentrate on the assigned mission and stay with the thoughts from the SFDPOT heuristics. Preparation for the product and domain-knowledge could have helped to focus on the msision.

Anne-Marie Charrett got on the discussion and explained that she created a wiki using firefox on an usb stick. Then she took the device to a Mac and saw that it did not port well to Safari. The problems seemed to be specific for the Mac, since on Windows 7 everything looked fine again. There were some cross-browser problems due to using the same file in both browser, but it was an interesting exercise overall for Anne-Marie.

Tony Bruce got on with his experience report. He got disctracted several times by the issue that he couldn’t use the browser’s back functionality to switch between different wiki pages. The name of the application was also missing from the web page title. Overall Tony experienced several bugs. Tony also found lots of documentation, some out of date, some relevant, but spread all over the pages. Since the main tutorial seemed to be out of date, Tony gave the recommendation to update it.

On questions from the participants, Michael Bolton explained that SFDPOT is a way to think about the coverage of the application under test. When going over all areas in the mnemonic – Structure, Function, Data, Platform, Operations, and Time – it will provide you with a good coverage, but when looking at all these things at the same time, you may very well end up on paralysis and don’t see anything at all.

Ajay Balamurugadas pointed out that he joined half an hour late, so he just had half an hour to test. He downloaded the application, read through the chat and the documentation, tried some testing stress testing, i.e. without Java installed, and logged a bug for the upcoming error message. After that he pretty much focused on the discussion.

Michael Bolton started out with some recommendations on how to improve the process of the weekend testing session, which was very much appreciated. On the product he continued that the documentation did not point out how to install the wiki. This forced testers to fiddle out how to install it and distract them from – well – actually testing. Michael mentioned the biggest problem to be a lack of documentation, since testers find out a big deal about the product by reading it’s documentation.

Michael Bolton continued with the recommendation to focus more on the usability of the wiki. The mark-up language is in fact very specific and technical. Most users wouldn’t bother to learn something new or get into the model that Wiki on a Stick prescribes in order to use it. Daniele considered the input from Michael valuable enough to re-think about priorities for upcoming features in the product.

The discussion continued for another hour on improvements on Wiki on a Stick. You may find the details in the session’s chat transcript.

Share

About the Author