This is an account of some of the activities I wish I had focused more on during the one-month Foundations course. The article is peppered with nostalgia for my fellow students and the activities we did together, but it ends with something awesome to look forward to: signing up for Bug Advocacy, the second part of the BBST course…
Last year, together with Catalin Anastasoaie, we started a series of one-day events under the umbrella of Tabara de Testare (“TdT”) with the purpose of building a testing community in Romania. It was a very interesting experience that helped us meet clever and skillful people from Bucuresti, Iasi, Cluj and Timisoara willing to share their experiences and learn from the community.
This one goes to all passionate testers out here: don’t make any plans for 26 -28 March 2012, as James Bach will be back in Bucharest teaching the martial art of rapid testing. So, get yourself ready for 3 days of intensive training, challenging discussions and mind-warping puzzles…
Michael Bolton will be returning to Helsinki for a new round of Rapid Software Testing course, on 16 – 18 January 2012. This time, the 3-day intensive class will continue with an open session focusing on methods and techniques for managing exploratory testing…
Having just returned from my first Eurostar conference, I’ve made a mindmap of all the sessions and tutorials that I attended and tried to include all the notes I had (if any) on each of them:
 |
| (opening the image in a new tab will allow zoom-in) |
Here are some of my thoughts in the form of questions and answers, which mostly come from feedback I gave Alex and Oana on exploratory testing when I first started out as a tester, and although much has changed since, I still have a lot to learn in order to become better at my craft… Enjoy! 😀
Q: So… pair testing; comparing the experience to testing alone, what are the things you did differently when testing with someone else?
A: Pair testing? Err… don’t you mean peer testing? Hm…
*thought about this for a while, then googled a bunch of stuff regarding peer/pair testing*
Okay, let me try to explain why naming it peer testing makes sense to me: …