Test Retreat

Welcome to the homepage of Kris Corbus

Archive for the tag “testing community”

Community Suffer


Testing community has something like bastard kid syndrome. We are there, we are doing pretty good, but no one notices that.

Desperate longing for acknowledgement.

That is what makes us all together ill.

By now it should be clear that no one will come to legalise us. Our happiness is in our own hands.

If you do not like ISTQB, than come with better idea, but stop simply complaining! Stop unfruitful debates who dare to be in community and who not, cooperate and collaborate to build it better! Choose testing “school” which fits you the best and start to contribute actively!

TestBash – I am finally coming!

This week is TestBash week. I know about the conference since its beginning, but until now did not managed to go there. This year is different! I bought the ticket as present to my birthday, company where I work offered to pay hotel and travel expenses. So here I am – with empty suitcase and head full of thoughts and heart full of expectations.

My TestBash schedule looks like this:


  1. arrival in Brighton
  2. Pre-Pre-TestBash Meetup – Games with Michael Bolton and John Stevenson


  1. Workshop1: Testing the Bigger Picture – System Architectures by Ash Winter
  2. Workshop2: You Love Load Testing? So, what’s next? by Mark Tomlinson
  3. Pre-TestBash Brighton Meetup


  1. Lean Coffee at Testbash
  2. TestBash Conference


  1. Post-Testbash Coffee Morning/Brunch/Breakfast
  2. leaving Brighton

I installed slack and twitter on my android. Will try to reflect for my dear colleagues. Let’s see how I will do it :)

Blog post from another TestBash newbie.

We are such a cool guys, why nobody loves us?

Software testing has huge public image problem and nobody really knows why. Or we do know why? Here is my version with main four points.

#1 You cannot study testing

Universities has tons of programs for applied sciences, but it is new to offer courses in software testing. Is it a real science? If yes – why I cannot study it? If not – why should I care?

#2 Anyone can test

How people get tester jobs? By accident! Wrong place, wrong time, no other opportunities, last chance to stay in company etc. I am no exception myself – my first testing tasks I got on my summer intern ship. Time to time all testing teams gets an offer to overtake bad performing developer, shop manager or other. While testers has a lot of empathy, usually they accept the candidate. In many cases it turns positive for both sides, but very important is a message to the outside: testing is not important, everyone can do testing, all bad performing employees we can relocate to software testing.

#3 Self confidence

What kind of people takes and sticks to the job, described above? My guess – people with low self confidence. There are many jokes about geeks, especially about their social skills and confidence problems. I see it applying daily for testers as well. Of course once you had a chance to attend local testing group or a conference, you will meet another kind of testers. But how many do that?

#4 Communication and other soft skills

No matter that every second tester says that communication is important testing skill, looks that we do it all wrong. We are testers, we tell people that we are trained to test a software with various approaches. For example, we observe piece of software as a black box. Sending signals in and analysing coming out signals.  If we would take a look to our image problem as a result of communication black box, than it is clear that we are sending wrong signals. Projects are different, customer needs are different, so why to keep focusing on found/open/fixed bugs? Why to use the same weekly report template?

And now?

Points above are my experience, lessons learned and observations. I found my way and can say that it works for me. For you I can suggest to learn your domain, to work on your self esteem and communication skills. Try to explain your kid or granny what do you do and why. Why one method is better then another? What do you try to find out? Why it is important to know? How do you collect and present the results? What profit has project manager, developer and a customer from this information? Use your experience as a solid base, but do not stop to look for new ways how to test. If your message has no advantage to other stakeholders than it is unnecessary.

Post Navigation