I am in a unique situation where I was hired as for QA with no computer background. How this happened is a long story but now I'm here, trying to become a useful and productive member of this team. Where would you start your training? What are some of the most useful skills to have?
- Anybody can ask a question
- Anybody can answer
- The best answers are voted up and rise to the top
The most important skill, I think, is learning about the product. Learn, learn, learn everything you can about your product and how it is used. That tide will float about half of your boats.
The other roughly half of your boats float on a different tide: your social skills. You need to do a lot of listening and offering support. Get to know the other people on the team and become known as the guy who says "yes I can look at that." "yes I can help you with that." Writing skill is part of this. Get to know users if you can.
When you combine social skill and product skill, it enables you to connect dots that other people miss. That's really what testers do (I'm going to assume that when you said QA you meant testing or something close to that): we notice inconsistencies that might be important and we report them.
Learning about technical things and programming is helpful over time. In some projects it's absolutely important. If you have gotten your job without that background, then it must not be considered critical in your project.
Also, take an honest inventory of what skills and talents you feel that you do have and consider applying this heuristic: get really really good at things you like to do, and find friends who can help you with things you don't like to do. That's worked well for me over the years. For instance, I like documentation, programming, and analysis, but I'm not very reliable when it comes to any repetitive or periodic task. I prefer to work in "episodes." So I'm better suited for test architecture work, consulting, teaching, or one time testing blitzes.
Formal training that you might need is: 1.Testing concepts/deliverables/processes 2.Testing organization 3.Defect Management process 4.Waterfall/Agile
Testins is definately not about learning theoritical concepts etc., It is more of application of common sense and functional knowledge. I suggest you start learn functionality of your application and follow below guidelines. If you still want to learn about testing theory concepts(which I'm afraid not going to be very useful in doing actual testing) I suggest you read http://www.tutorialspoint.com/software_testing/ and be done with learning theory. If you want indepth learning of theoritical concepts CBOK CSTE (http://www.softwarecertifications.org/cboks/cste/skillcategories.htm). You are not going to learn more theory than that. Coming to what is important in real world testing, I would suggest you concentrate on below points.
All the best.
If you want to be only a good QA employee then start knowing about the product of your company.
But if you want to expert in QA then you have to "practice" a lot.Remember you are the master of your own.No body will help you to learn.You have to find your way and that is only possible if you start practicing.Question is how to start?
1.Try to join weekend testing group.It will really help you to improve your skill.
If you want to learn something then start writing a blog on that topics.But don't copy from other source just read that topics from any source (Its may be from books or online resources) and then start writing that to your blog.Try to explain that topic from your own.This is also a good way to learn.