I love communities, hanging around smart people that have their main interests of which they are really passionate and also often very good at. Personally I prefer blending into different communities, getting some of many different things rather than to delve very deep into something in particular. I think its my curiosity and kind of systems thinking mind that wants to stay up to date with a lot of things. I also like to keep my spectrum broad with regards to the knowledge I take in, and then I can filter the good parts myself. Read more…
When working with our mission of creating an organization wide test strategy I was thinking about quality related problems we have in some projects. I realized that the expected quality is not explicitly stated anywhere. This means neither customer nor development team are aligned about which level of quality is expected to be delivered when done. I needed something to achieve a better awareness of quality requirements and a light weight way of stating them explicitly. Read more…
After seeing so many of these “this is my profession and this is how different people see it” on Facebook, I decided I wanted to give it a shot for software testers. A couple of minutes searching and pasting gave me this.
Give me your feedback, but remember (1) it is a joke and (2) I am not a creative artist. If you have better ideas on how a software tester meme should look like just go ahead and make your own.
Now I am going to continue my vacation.
For quite some time now I have struggled with making note taking a natural part of my personal progress while testing. And well, I can say that it has really made impact on many other aspects of my work in other situations as well. I am actually quite proud to say that it has made great impact on how I perform in general, and how easy it is to make follow ups when done with anything. Now I would like to take this some steps further to explore how my notes can give more value to the whole team in a project setting, both mine and the teams’ collective notes.
The delegates of the second Swedish Workshop on Exploratory Testing (Test Planning and Status Reporting for Exploratory Testing) were:
Henrik Andersson, Azin Bergman, Robert Bergqvist, Sigge Birgisson, Rikard Edgren, Henrik Emilsson, Ola Hyltén, Martin Jansson, Johan Jonasson, Saam Koroorian, Simon Morley, Torbjörn Ryber, Fredrik Scheja, Christin Wiedemann, Steve Öberg
This weekend I attended SWET2 in lovely Hönö, Gothenburg. Great surroundings and nice weather accompanying great discussions about exploratory testing. With the experience and great knowledge of the delegates and a good structure maintained by moderators, the levels of knowledge sharing was huge. And I was amazed how long we could discuss those nitty gritty details of a subject. And that gave me some input on some triggering words I would like to share.
Update: The trigger I got for the whole post was when Johan Jonasson mentioned his trigger words at a conference this week.
In my perspective, these are examples of words to use with care if you really want to get something out of your discussions with others, without ending up tearing these wordings into pieces.
Pradeep brings up the skill of writing influential emails as a tester. I cannot agree more on the need for it. Here is what I wrote as a comment to his post. Please feel free to add more comments and give me some suggestions on rules for improvements.
Hi Pradeep! I like the way you bring out the need for good writing skills as tester. However, I am not very sure you showed us the very best answer to your own question. Actually, I think Sreenurajs last one was better. Why? Read more…
Recently my consulting company migrated all our email accounts to google apps. Even if the main reason was to get the emails on a new platform, this was a good step for our entire infrastructure, where I found a good and easy-to-use tool for my testing and note taking.