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.
Can I already post my submission? Oh, I don’t care anyhow , here it is: https://firstname.lastname@example.org/about-a-non-technical-skill-that-every-tester-should-have-8960ab14e01
Haven’t had much time recently and got into blogger laziness so here is my rushed and impressively lame effort, sorry.
I actually had this half written a week ago and forgot.
Imagination! Being able to figure out every tricky way a user will use the system (almost none will do what the manual says).
Below would be my top non-technical picks for testers:
By communicating you are sharing your ideas of what you just explored or what is the error in the system.
By collaborating you are broadening your horizon and skills as a tester and looking at the big picture and also helping others think like how you do
Communication and good approach toward your team.
Remember, as a testers we are looking for someone else’s mistakes and what someone did wrong.
No one really likes being pointed at all mistakes they have made so testers approach toward developers and toward client when talking about Issues and Errors is the most important thing for a tester to have in my opinion.
Since again, you have to report to a Client what your team (for which hours they are paying and every mistake is costing them more money).
So would say, testers need to have great communication skills.