Sprint 4: What’s the non-technical skill that every tester should have, but most don’t seem to?

(Lee) #5

This is a tough one as I imagine I’m not alone thinking there are multiple answers to give. This is a prompt I can definitely work with though :slight_smile:

(Melissa) #6

Speaking and writing skills. Presentation skills. Leadership skills - and I don’t mean managerial, I mean the kind that let you get your point across without going red-in-the-face. If someone had started me off with those kinds of leadership skills, I’d be miles ahead in my career for sure. There is also the case that one can only learn those with time… but it would have been nice to be mentored into it.

(Kim) #7

Agree, that’s why retros are a great place for the team to work together, assisting ones who have an issue getting their bug or note writing clear enough for anyone to understand

(Ady) #8

Empathy. For users, for team mates, for yourself

(nicola) #9

How to talk about their testing and what they h ave done in daily stand-up so that others actually know what they’re doing (not just “testing”)

(Lee) #10

I would probably say tenacity. The ability to articulate their point well and stand their ground if they feel the need to defend their viewpoint.

Unfortunately sometimes allowing yourself to not be easily manipulated is important when testing software (especially when faced with strong bias!).

(Kris) #11

Similar to a few other comments; I find in more junior QAs it is the “fear” of talking to more senior members of the team (PO, SDM, Dev) about a valid bug they have found. They have the fear as they don’t think their bug will be taken seriously or that they will look down on the them for finding the bug. However I always tell the junior QA just to do it - get all the evidence you can to prove it is a bug, triple check, and then if you really need to approach someone more senior team member just do it…you can’t not be confident with triple checked facts, and anyway, if you’re wrong it’s your job to find bugs.

(Adam) #12

Understanding how to argue properly (i.e. from a solid factual basis), and how to counter fallacious arguments. Going back to the previous sprint’s topic of useful books, Carl Sagan’s “A Candle in the Darkness” has excellent coverage of the types of false arguments.

(Silvia) #13

The ability to find the balance between having self-confidence (to defend the defects they find) and putting themselves on developers’ shoes (to not hurt them when they talk about the errors)

(Shivani) #14

The ability to realise that the scope of tester’s responsibility is way beyond releasing product. Keeping eyes on logs, monitoring also comes in their plate.

(Daniel) #15

All of these ideas are excellent and certainly deserve a blog post with more detail :slight_smile:

I’ve written my own blog post. A slightly different idea from everyone else, and it’s a simple one: it’s to get away from your desk!

(PRACHI) #16

Honestly, if you would have asked about “technical” skills, the list would have been longer.

I second the opinion of people who talked about communication skills or ability to explain to BAs or developers or even senior management.

(Heather) #17

It would be nice to see some more blogs posted here as part of the Bloggers Club. Doesn’t have to be a long blog :slight_smile:

(Lee) #18

I keep meaning to write one for this sprint!!

(Paul) #19

I see nobody has mentioned “Common Sense” yet… :thinking:

(Dominic) #20

Loads of great ideas here!

I’ve just gotten back in the office and I’m ready to write something this lunch time. It might end up being about coffee since I really suffered its lack in Canada (well my kind of coffee anyway)

(Mary) #21

You have to understand who will be using the application you are testing and be able to think/work as they do. Are they an office worker who does their job while talking on the phone, to a co-worker, etc. and inadvertently hits the wrong combination of keys? Will it be the office worker who is dependent on the application to do their daily job, therefore they will do everything in their power to break it when they see it to limit their down time? Think like a user, not a developer.

(Adam) #22

Can I already post my submission? Oh, I don’t care anyhow :slight_smile: , here it is: https://medium.com/@adam.hepner/about-a-non-technical-skill-that-every-tester-should-have-8960ab14e01

(Paul) #23

Haven’t had much time recently and got into blogger laziness so here is my rushed and impressively lame effort, sorry.

(Ben) #24

I actually had this half written a week ago and forgot.