Just as a continutation of another thread somebody asked about how to asses a tester. The primary info supplied was mainly bug oriented i.e. number of bugs, quality of bug reports etc. However there are many other aspects.
Many of them are discussed in a recent thread "How to evluate test work? ".
Robert from what you say it looks like you have more of a job description, for all levels in QA dept. Could you share them ?
never say die
[This message has been edited by witchcrop (edited 07-20-2002).]
No they are not job descriptions, they are what I persieve personally that a tester should be aware of at each level in an organisation. Job Descriptions are determined primarily by the role. For example I have worked as a Test Manager whould physically does the builds but where I am now I don't
<BLOCKQUOTE><font size="1" face="Verdana, Arial, Helvetica">quote:</font><HR>Originally posted by canetti: Has anyone ever worked for a company that has done a skills assessment for a software tester? What are the general skills and specialized skills that a good tester should need?
We have done some skills assessments and I know that some of the things they have looked for are:
1. Creativity & Logical Thinking (or really the ability to learn)
2. Organizational skills (at least its a plus if you have it)
3. Good Writing Skills for detailed/clear test plans/cases, etc.
4. Communication (This is a big one, to be able to listen and then to speak)
As for specialized skills it is definitely a bonus if you know the language(s) that you are testing and if you know the hardware/software of the system. But in my opinion if the person has the above 4 qualities, especially the ability (or motivation) to learn than I figure that they can be trained on how the hardware/software works or how to analyze code for issues. (They may not be able to write great programs neccessarily but they can look at the code and see major issues anyway)
A test automator needs to have good testing and development skills. He/She needs to understand testing requirements and the situations testers face. Automating tests should not be an opportunity to impose a particular testing methodology on testers. They will find fault with it and refuse to use it. Rather it needs to build from existing testing methodologies.
If the test automator has background as a tester, you will need to ask if he/she will show the necessary discipline. Sometimes testers who really want to be programmers seize on test automation as a way for them to develop these skills. It is important that they have good judgment and not get carried away with the programming. Be wary if they are hoping to automate all of their testing. They need to be focusing on the big wins. They may focus on improving the automation when it is actually good enough for the job.
A test automator needs to know how to develop software. He/She needs to be particularly aware of issues such as maintenance and reliability. Making the system easy to update with changes to the product under test should be the priority.
If his/her background is as a developer, you will need to ask if he/she has understanding and respect for the testing process.
Sometimes you can find independent contractors who have well-matched backgrounds. With them, you will have to ask who will be maintaining the testing system after they have left. Maintenance will be a critical challenge.
If you have access to good training in test automation, take advantage of it. Developments in test automation are being made very quickly. It's often cheaper to pay to people learn from someone else's mistakes than to have to make them make the mistake again themselves.
Don't assign automation to rejects from programming or testing. Unless test automation is done by someone who is motivated and working closely with the rest of the development group, it will not succeed.