On the other hand, there are genuinely skilled testers who think about what is right to test and test it right. It is indeed a small proportion of the whole testing community. In another group I mentioned that skill comes from experience, training and education. There are barely any schools which provide testing education. Very few testers try to update/upgrade their skills and there are experienced testers who do not update their skills at all.
I posted this discussion to many groups and all seem to agree that testing is a skill. The problem is, it is hard to find.
ctive test professional. I would not hesitate to say that not everybody or anybody can become tester! Earlier, testing was considered as an art. Now, gradually it is evolving into science & engineering with methodologies, process, methods, techniques and tools coming into testing arena.There are institutes that provide education on software testing exclusively.
I believe there are software testing training institutes, but I am not sure how effective they are. My concern regarding software testing has been authentic college education of this field.
As everyone here is from testing background and we need to prove to ourselves that Testing is Skill.
First of all , I want to focus on word ‘Skill’ which will help to explain, why testing is skill.
A skill is the learned capacity to carry out pre-determined results often with the minimum outlay of time, energy, or both. Skills can often be divided into domain-general and domain-specific skills. For example, in the domain of work, some general skills would include time management, teamwork and leadership, self motivation and others, whereas domain-specific skills would be useful only for a certain job. Skill usually requires certain environmental stimuli and situations to assess the level of skill being shown and used.
If you carefully go through the definition, you see where i want to drive You. Testing is skill if you can –
> Measure product quality in quanative terms. Irrespective of knowing
that Product is defect free or not.
> Draw a visible line in product quality before testing and after.
> Add you domain knowledge as catalsyt which always help to minimize the
unexpected behaviour and improve the trust among stakeholders for testing
and their knowledge.
> involve yourself from scratch in SDLC and your knowedge/experties (Domain)
helps team to design/develop a robust/user friendly system.
To design a skill set for testers depends on the areas where you are working and it is very procedural. Please add your comment based on your respective areas which will help everyone to know and improve.
It is also natural to define objectives in terms of our own knowledge base and skills (because that is what we know). But often systems have different aspects depending on who is looking at it, and so you usually need to use a broader audience.
I think this applies to test teams and plans as well as other topics (such as requirements gathering) to ensure that you have skills in a team that ensure that all aspects of the system can be covered.
Meeta Prakash • True. But I would not say “outsiders” only. It becomes generic and dilutes the understanding. In your case, it was a business leader. So we should ideally understand the roles and depth of understanding each of them need to develop for themselves.