Rapid Software Testing (RST), even in scope of the class, is a huge topic. My account is a glance of it, not even outline. If you want to know more, you definitely want to read open course description and materials.
RST class delivers on what it promises. That’s important. Again, you want to check the course materials on what is promised. To show a bit of what is promised, I’m using two slides from the course public slides.
That all gets demonstrated in the class.
RST lives up to its principles. Important part of the class is asking questions, not only about testing exercises, but about what you want to know of class topics and other topics of testing. Don’t hesitate to ask about what testing problems you may need help with. Important point is that you have high chance to get in the class explanations and examples you ask for.
RST does not have “finish point”. Learning must not stop on final class day. RST brings in many topics and it does not have to end. For unprepared people course may be a starting point, for people who followed RST before taking class it is like a waypoint. Both types get a lot to continue to learn and to develop.
As it is promised, every category of participants can benefit from RST class. Unprepared participants get something new to think about, see more ways to do testing. Prepared see how this works in action and practice it. Even if you listened to several talks / podcasts of RST, “it’s one thing to read about riding a bicycle and completely different thing to ride a bicycle yourself”.
Unprepared participants can see that testing is way more than “test cases”, get opportunity to break free from factory and test case thinking. They also test in exercises for 3 days without writing single test case. Prepared get tricky exercises and “food for thinking”, practice testing in sessions and in cooperation with other participants in class.
Some topics we learned and discussed: what’s wrong with test cases, how to start testing something instantly without following lengthy procedures, where to get information for your testing, what your oracles (entities determining what is a problem and what is not) could be, when to stop testing, how to put coverage without counting test cases, what heuristics may aid your test ideas, how to think about product-associated risks, how to explain to others why testing takes so long…
Although you get certificate in the end of the class, IMO it is important to realize that RST is not about certification. You learn, you practice, you get leads to learn more, you get “entry ticket” to community where you can ask more. Thoughts, heuristics and connections you get with the course are much more important than any certificate.
Keep in mind that RST is a lot about time, “How use the time I get better”. While it may be not emphasized every time, the questions brought up in the Kiev class, like “Why not test cases?” and “How to learn newcomers?” or “Can we get rid of testing role?” are about use of time too.
Back in 1990s guys like me were fascinated a lot with action movies, since then we use meme “Show me your kung-fu!”. In some way RST is like kung-fu we saw in movies: there are no “kung-fu” cases, you learn from other people, you practice a lot, you have to be always prepared to show what you are capable of. Also, like martial arts have connection to thinking and philosophy, RST does too.
If you wonder “What the course content is about” and you are interested to learn more about RST, once more, please read open course materials and documents (section “How Students Should Prepare”) .