Tag Archives: softwaretesting

An affidavit of sorts

The last three months I’ve worked specifically with the goal of my testers taking responsibility for their work.

I’m a strong believer that each person is responsible for their own lives. I try to  live by it and I expect others to do the same. Its one of the reasons why I endorse and believe Exploratory Testing is so powerful. The tester becomes centre to the testing. The tester is the decision maker responsible for their decisions(good or bad) and must be willing to stand by their choices and defend them where necessary.

Its a powerful concept, and I think somewhat alien to the way we are brought up and perhaps bring up our own children. Instead we are protected or we try to protect, wanting to prevent harm to those we are close to. Actually, I think its impossible to totally protect people, much better to teach survival skills.

I often hear people saying: “A great test manager removes obstacles so that their team can test” and its true. A good test manager will do that. However, I think a good test manager will also allow their testers to fail. Allow them to make their own decisions and learn to stand by those decisions and then defend them.

If we don’t do that, are we really helping testers to learn and grow?  I wonder.

I’ve had the luxury of procrastination over the past two days. Yesterday, I spent a glorious few hours at the Seattle Art Gallery. It was the perfect antidote to CAST 2011, which was exceptional yet mentally exhausting.

I also missed my flight back to Sydney, which meant I had a second day of whiling away hours at Seattle airport.

Our brains are so fascinating, aren’t they? Just as I’m about to board the flight, a burst of insight and determination hit me. I guess all that procrastination culminated in my powerful thought.

Its this.

As we learn and grow as testers and human beings, we constantly need to revisit our beliefs, values and motivations. I realised mine needed a revisit. (Incidentally, my tutorial at CAST was on this topic, another example of “if you want to learn something, teach it!”)

I needed to rework my ideas, goals and what was important to me. I needed to put myself in the centre of my testing career. I’m responsible for what I do and what I learn. Me. No-one else. Not mentors, not other testers, not thought leaders. Little ole me.

A few testers at CAST really inspired me to be like this. Unfortunately, I don’t know their names or else I would cite them here. But they’re not thought leaders or mentors, they’re context driven testers with a mind of their own. I like that.

I’ve always been able to think for myself but sometimes, you just have to up the anti, you know?

I don’t know what this will mean for me. I’m not sure where it will lead. What I do know that from this point on, I will continue to own my decisions and I will stand by them, just as I encourage my own testers to do.

I guess thats it. Its just something I wanted to share with you all.

QED

Keeping the lights on when your battery is running low

Image of Battery

Most of when I test I’m thoroughly engaged and involved and enjoying the moment. Then there are those “other” times.  Typically for me they happen in the afternoon. My sugar levels get low, I get tired, and I stop testing well.

But darn it, there’s so much testing to do! How can I and my team continue to test effectively?

The biggest trap to fall into is to continue testing without changing something. Testing’s too important to be performed without full use of mental faculties.

Its up to me to ensure I keep alert.

Here’s my list:

1) Eat!
Sugar levels are low: Have you had lunch??? No….Okay, this is basic, but don’t skip lunch. Your brain needs nourishment for all that cogntive work it has to do in the afternoon.

2) Take a break.
It sounds counter-intuitive but by taking a break and doing something completely different, gives my testing brain a break. I like to do something physical,like going for a quick walk.

3) Swap a feature
Ask a tester to swap areas with you for a while. A mental change of scenery if you will.

4) Make it enjoyable
Find some way to make testing a bit fun for the team. Perhaps

3) Use the Trish Khoo method
At the start of a testing iteration, she asks the question “What can I do differently” or “how can I make testing more fun”? What a great approach!

There’s other ways to take breaks too.

4) Talk to a tester

I have to watch out for this one, as I need to take into account other testers may be “in the zone” but if someone is free its great to have a chat.

5) Talk to your peers

Again, timing is the key here. I find this one very invigorating, it also helps me take a step back from my immediate focus and see the “big picture”

6) Tweet, Blog, Share

I’m finding this one a bit hard at the moment as the company I’m doesn’t allow skype or twitter. But when I can, I use my phone to keep in touch with testers outside where I’m working.

For me its a mixture of making testing enjoyable, taking breaks and mixing things up.

What do you do to keep alert while testing?


 

How to write about software testing

Based on the number of requests I’ve had to write articles recently, there seems to be a big demand for testers who can write  well about software testing.  I’ve been asked by a few different companies to write articles on their behalf. Sometimes I’ve been asked to write posts for someones’s blog. I’ve only done that once with Quck Testing Tips which was a lot of fun. But generally, I find it hard enough to be inspired on my blog, let alone writing for some-one elses!

I thought putting down what helps me, might help a few testers out there. Writing well is a great skill for a tester to have. Think of all those persuasive bug reports you will be able to write.  Its also a great way to consolidate and  refine your thinking. (A great read on this topic is chapter is Maria Hammeren’s chapter entitled “writing as a method of reflection”  in the book Dialogue Skill and Tacit Knowledge.)

1) Write from the heart.

Personally, I’m only motivated to write when I have something I feel passionate about. Thats a good thing because you can create a bond with the audience. But it can be unhelpful too if other people are relying on you to write something.

Perhaps passionate is the wrong word, but  writing posts that resonate with you reach out in some way to your audience. Perhaps its the choice of words you use, I’m not sure, but your readers will pick up on your sincerity.

2) Be yourself

That is, don’t try and be the expert unless you have personal knowledge about what you are writing. In practical terms, avoid trying to sound more experienced than you are. Be honest about your experiences.If you do write on a topic (say automation) in a authorititive manner, you had better be able to back it up with fact and substance.

An excellent example of someone who does this  well is Michael Bolton. I believe in what he writes because he cites references and backs up his statement with examples and facts.

Nuff said.

3) Give yourself Permission

I have James Bach to thank for pointing this one out in a tweet*. Its so true.
Give yourself permission to write your thoughts. They do count and they are of value. Trust me on this one. A great example of some-one who does this is Lanette Creamer. I admire they way she is so forthright with her ideas.

*tweet info with nod to Michael Bolton for supplying it

[quote style="boxed"]As a teacher this is key: Permission givers http://bit.ly/9qnyOt (thanks @jerryweinberg, for the link, and the permission)[/quote]

4) Proof Read

I tend to write posts 2 or 3 times before I let them loose on the world. Seriously. This is how I work.

a) Write down sentiment anyhow, anyway. Don’t worry about what it looks like
b) At this point I  feel free to explore, sometimes I stray from my originally intended topic to the point where I have a compeltely new article.
c) Read the post (try reading it aloud), and rewrite it, move paragraphs around to get a better flow. Cut out paragraphs that prevent a nice flow through the post
d) Take a break, do something different
e) Come back re-read the post, edit it. check for spelling then send it

A trap you can fall into though is over proofing. If you feel really strongly about something, and you leave it to the next day, you may chicken out and decide not the send it. Sometimes posting in the heat of the moment is a good idea. (Hey I never said writing was clear cut!)

5) Give credit

If you get an idea based on a book you read, share that. If something inspires you, share the link.

6) Be Original

No-one wants to hear trite stuff that parrotts what others say. Believe me. Make your content your own. If you are talking about a hot topic, try and put your own personal spin on it. What are your thoughts on it? Don’t parrott a thought leader, their stuff is far better than yours anyhow.

7) Be Precise

Often its a struggle to come up with a precise word that reflects exactly what you want to say. But please, don’t be lazy about it. The english language is diverse and there’s bound to be a word that aptly describes what you want. Use a thesaurus if you have to, or do what I do and wait until the right word comes to you. Your readers will appreciate it.

8 ) Why do you write?

Here is Bernard-Henry Levy on his view on writing. Great stuff. In particular what drives him to write is interesting:

[quote style="boxed"]I am not writing to be loved. There is as much pleasure to being hated as being loved. I write in order to convince. In order to win. In order to change, even just a little, the world. I recently launched an appeal on Twitter supporting those attacking the official websites of the Tunisian regime. An intellectual calling for hacking doesn’t happen very frequently, and there is a stir. I am happy that it succeeded. I care about being heard.[/quote]

Whats your driver? Is it your ego, is it SEO ratings or is it something else? I started writing to get ratings for my website, but now I write for the pure joy of writing, because I get a kick out of crafting a beautiful piece of work.

9) Practise

The only way you are going to get any good at writing is by practicing.  How are you going to practice, well thats up to you, but writing a blog is a good start. Don’t aim for perfection, just get out there and write something. I will never forget my first blog post. It was the equivalent of hello world! (I wish I still had it, I would link it here)

Well, thats it. Nearly

There is one more thing.

If you are serious about writing skype me on charretts. I offer free coaching and I’m willing to include writing in that scope, as long as its to do with testing.

[By the way, when I'm talking about writing, its mostly in the context  of articles, blogs etc.]