Skip to main content

RTI - training for testers in Bratislava

I wanted to contribute into the testing culture of my company, so i decided to lead a training.

I was trying to condensate the Rapid Testing Intensive online 3 days course from James Bach and Michael Bolton into a 6 hour training class.

It went in my opinion quite well. I don’t want to reproduce the theory part of it, which you can see here

The practical part was more interesting, each of the participants was testing an freeware screenshot tool (which I rather don’t mention here), we were suprised how many bugs we found on an publicly used tool, some of them crashing the whole application down.

Our Mission:


Whole testing took over 2 hours and we had an interesting review session afterwards. The output of which was afterwards this Test Report.

Test Report

Results:

- The product's basic functionalities work. Non-typical scenarios produce unstable and unacceptable results,
 there are also minor bugs that are acceptable
- There are a few specific scenarios resulting to the application crash
- The application is hierarchically unintuitive in several instances
- There are indications that the portable and installed versions differ
- Mutual agreement on our recommendation -> Buy only under the condition that the known bugs are fixed and deeper testing is conducted thereafter

Testing:

- We performed paralelly 4 sanity check sessions by different testers to gain both confidence in the results and remove possible subjective factor
- Each session was 120 minutes long and a group review was following these sessions

Caveats and recommendations:

- Bug fixing followed by retesting is required
- Additional deeper testing is strongly recommended - various platforms, resolutions and monitor devices are recommended to be used
- Redesign and comprehensive manual is needed to be delivered

Comments

Popular posts from this blog

When to start automation?

If you are asking this as a tester, you probably asking too late. Automation is something that can save you some portion of your work (understand resources for your client) and i rarely found cases of testing work that did not need at least some portion of automation. I know that it is rarely understood that automation is something to be developed & maintained and if you cover enough of the application, you do not need any more regression - well i do not think that somebody has done an automation regression suite that if fully reliable (i am not speaking about maintaining this code - which is another topic). There can be always a bug (or quality issue) that slips through, even when you scripts go through the afflicted part. I understand that many testers have no development background or skills, but i doubt the developers that could help you are far away. I am not assuming that they can do the scripts for you.... However if they understand what you need, they can say how e

Testers toolkit

As every craftsman needs his tools, testers are no exceptions. I was this weekend at  SOCRATES SWITZERLAND  (SOftware CRAftsmanship and TESting) where we talked also about useful everyday tools. This list tries to be as general as possible to provide tools which can be useful to most part of everyday work, more specialised test-useful tools are very context dependent. I use most of the tools mentioned here and believe they can provide value also to you. Documenting Screenshot  - good picture is worth thousand words, this applies especially for testing, the following are some screenshotting tools and editors I used and can recommend Lightscreen  - simple tool for capturing pictures, free, cannot edit the pictures FastStone  - screen capturing tool and editor, cheap & gets the job done Snagit  - very powerful screen capturing tool and graphic editor, many functions which you never knew you can do, but wont be able to live without afterwards, a bit pricey Recording  (

Many problems with one button

I admire the complexity which can emerge from elementary designs. Especially in the problem space. One example speaks for itself, the 'On/off app' : - an webapp consisting only from one button which can either turn 'things' on or off ( 'Picture 1 ' is an aproximate illustration of both visual states of the app) - 'things' are marketing campaigns, some more complex processes to send particular marketing messages under particular conditions to particular customers (details of such don't matter in this context) Picture 1 source: https://www.vecteezy.com/vector-art/88994-on-and-off-chrome-buttons Even when my team was highly qualified in software development, under the fog of communication  and implicit expectations that we missed, we discovered the following problems with the implementation:  Wrong template The template which we used in the test environment was not meant for production, the impact was low - only a few business