Hello, my name is JeyZ and i am a student of computer engineering career.
I started to work as tester and me and another workmates are discussing what skills that make a good tester are.
Ņwhat do you think about it?
Thanks and I will wait your opinions.
ya skills required for a tester
1. manual testing concepts
2. some basic knowledge about the tools
3. networking basics
4. database knowledge
5. some scripting and programming knowledge
6. written skills
7. most important is you should have testers mindset
like thinking as a real user, negative thinking and last but not the least patience.
1.Love what you are testing.
2.Be a user in your test not a tester.
3.Look at the big pic and then search for the details.
4.Check all the scenarios in every specific feature.
5.Remember (write down)your moves to reproduce a bug.
6.Find a good title (summary)for the bug
7.Write your moves clearly and make sure if someone will do your moves he will rich the bug.
JakeBrake, according to article you linked to good tester are primary zealous about process/methodology following (creating artefacts accordingly).
I tend to agree with the simple folk posted here rather than Elfriede Dustin, testing book author. On the other hand stickyminds are basically for PM and I must admin (unfortunately) thatís the way how PMs will typically evaluate testers.
As they zealous believe requirements provide all the information required for tester. They donít know about grey box testing, do they? http://geocities.com/xtremetesting/GreyBox.html
Testing is an art of extracting information from all sources and the art of delivering the (processed) information about the findings. And the best source and the main information target is a programmer who wrote the unit under test. That does require technical skills (to be able to communicate with the technical person - developer) a lot of people skills all mentioned here including salesmen and story tellers.
?:the art of a constructive conflict perceived as a destructive diagnose.
The difference is that Jake's article gave good information for someone who asks, "what skills that make a good tester are."
Your link doesn't answer that question.
Having read it, I am not sure what it IS trying to say, other than it is a good idea to investigate the code reasons for errors and work between black and white box testing. Even if someone is adopting a Grey box testig approach, they still need the essential testing skills and mindsets Elfriede mentions in the StickyMinds article.
"Not every solution was derived to address an obvious problem" - Me (quite recently indeed)