Take the 2-minute tour ×
Programmers Stack Exchange is a question and answer site for professional programmers interested in conceptual questions about software development. It's 100% free, no registration required.

This question already has an answer here:

I have a very small 3-developer programming team that has zero QA people. We would like to hire a QA person but are unable to at this time.

Until we can hire a QA person with proper QA training we're going to have to test each other's work. I'd like to hear from anybody who has done this, how one does such training.

I am an expert developer, and I respect QA as a separate profession. I don't think I think like a QA person, but I need to start thinking more like one. In the absence of other people doing this job, some of it will fall to me.

Is there any book, or tutorials on How to Do a Good Job at Testing and QA on a software product that addresses the idea of teaching a programmer to do QA?

Similar question here suggest to them that they run their team with Scrum, which we are currently working towards, but we will have to do without a QA person at least until our team size can increase.

share|improve this question

marked as duplicate by gnat, Bart van Ingen Schenau, MichaelT, Walter, Joris Timmermans May 6 '13 at 12:01

This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.

    
our colleagues at SQA.SE have some recommended resources listed in answers here: Suggested books to start on software testing –  gnat May 28 '12 at 9:24
    
possible duplicate of Should a developer also act as a tester? and of Are programmers bad testers? –  gnat May 4 '13 at 9:16
add comment

2 Answers

If your team is 3 people, hiring a QA person is a really bad idea.

Put away the idea that finding bugs in the code is the QA team's job. Testing the code, including all the phases of testing (including unit, integration, system and regression testing) should be a function of the development team. Own the quality of your code.

If your team lacks skills in this area, provision some resources for reading and training to fix that problem. Questions about what training resources to use would be a good basis for a separate question (though it may be a dupe).

share|improve this answer
    
Well, this is definitely the way to go if we're going to take Lemons and Make Lemonade. We definitely need to own our code quality. The problem we're having is we don't think about how to break the app code the way QA people seem to do. –  Warren P Jun 1 '12 at 21:38
add comment

You are mixing up Test with QA. This is a big mistake - It's like calling an accountant an auditor - both are highly trained professionsals, and auditors often come from an accounting background, but just like Auditing is not accounting, Quality Assurance is not testing.

Test is the process of looking for defects in a program. QA is the process of preventing defects in a software product. One of the inputs to a QA process is test results from Test engineering, as are code review, code metrics, requirements changes.

Work out if you are wanting to improve your testing, or your quality.

share|improve this answer
    
Umm. we want to improve Both. Starting with discovering bugs (testing) and then preventing them, too. Here on earth everybody mixes up test and QA. QA/QC/Test = a single role or department in most places. –  Warren P Jun 1 '12 at 21:39
    
@WarrenP - Obviously we do work on differnt planets - my world involves Aerospace and life critcal systems. I happily accept that you (an a majority of programmers) currently disagree with me (and the Aerospace/life critical systems indusrty) as to the difference, I believe you (and all the other programmers) would benefit enourmously going out an learning the difference, Only then can you decide if testing will improve quality in your particualr situation. –  mattnz Jun 2 '12 at 22:23
add comment

Not the answer you're looking for? Browse other questions tagged or ask your own question.