Category Archives: insight - Page 4

Where do I go from here?

In two months to this day, I will be giving my tutorial on Career Management for Software Testers at CAST 2011, in Seattle, USA.

Any self respecting software tester has asked themselves at least once in their career. “Where am I going with all this?” or “Is this role really where I want to be for the next x number of years”?

If you look around, its traditional* to think of a software testing career path as follows:

[quote style="boxed"]At entry level as a Tester, you’ll primarily be performing test execution and acquiring niche skills to ensure systems meet performance standards required by the business and end-user.
Progressing to Test Analyst and then on to Senior Test Analyst, you’ll work on more complex scenarios, become involved in requirements analysis and test case design as well as execution. As a Test Analyst you’ll also be able to become involved in the specialist areas of Test Automation and Performance and as a Senior Test Analyst you’ll start taking responsibility for junior staff.  [/quote]

I think that’s a real shame that the role of  Test Manager is considered the pinnacle of your career. Why is it that in order to advance your career you have to be seen to me leading people?

So, I want to show testers that there are other career paths. In my tutorial we’re going to take a look at some of the typical roles testers in testing;  That of a tester specialist, a test manager and a test consultant.

But you won’t have to listen to me share about it, I got some fantastic software testers who have agreed to come in a share their own personal experiences. Karen Johnson (Test Consultant), Fiona Charles (Test Manager) and Markus Gärtner (Software Tester) will be available to discuss the pro’s and cons of their respective roles and understand what skillset you may need to get perform these roles.

I’m looking forward to giving this tutorial. Why not join me at CAST 2011? There are still some spots available.

*sourced from Planit website

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.]