Answer Posted / artak gasparyan
A team approach ("Buddy Testing") to coding and unit
testing. Using this concept, two-person teams are identified
and assigned programming tasks. Developer 'A' writes the
test cases for Developer 'B's specification before Developer
'B' begins coding. Developer 'B' does the same thing for
Developer 'A'. There are several advantages to this technique:
1) Objectivity is introduced into testing at a very low
level, which is seldom achieved during developmental testing.
2) By creating the test cases prior to coding, they can
serve as models of the program specification requirements.
Most developers will find that having the test cases
available prior to coding actually changes the way they
write their code. The test cases are designed to break the
code as well as show that it works. Many developers who
write test cases after coding merely demonstrate that their
code "does what it does." Don't underestimate the power of
buddy testing. This is applying the principle of
preventative testing at the lowest level.
3) Finally, buddy testing provides a certain degree of
cross-training on the application. If developer 'A' leaves,
then Developer 'B' has knowledge of his or her code.
Chpter 4 - Unit Testing
"Systematic Software Testing"
by Rick D. Craig and Stefan P. Jaskiel
Artech House © 2002
| Is This Answer Correct ? | 0 Yes | 4 No |
Post New Answer View All Answers
Write the 10 high test cases for making video call/face time?? Write the test cases for credit card accessing the money transfer?? Write the test cases for file transfer from one user to other from Google Drive/drop box?
I have interview on Guide wire testing. If you please share me.
How does quality control differ from quality assurance?
hi friends, i have completed course and project on insurance domain in mindq testing institution...can any working employee please tell me ,which notes( testing subject notes,project notes)i have to prefer first.i was studied both notes and getting confussion.one of my friend got job throughly only project notes and said that project notes is enough to get job.in which way ,i have to prepare interview( which important topics first ), if you are follow any strategy to interview purpose,pls send me important topics list.
Which was the most interesting bug you found.
1.For a single module how many builds are possible 2.what will be the max or min time to finish up an single module
To specify the test artifacts involved in testing.
Password is having 6 digit alphanumeric then what are the possible input conditions?
what is test strategy,test plan and test policy?Does anyone have dummy documents or any links that gives more idea about these?I am a beginner...interested in learning more abt testing.plz help and encourage me........!
Can any1 tell me suppose u r doing manual testing on unix platform with Shell Script, then how it is done? How u r implementing it & what is the use of Shell scripting on Manual Testing?
test cases for Insurance Processing System ?
What is Difference between Test Strategy and Test Methodology?
What are differences in testing a client server and a web application?
Which is the best book to ref. for design the test cases/scenario in manual testing,which gives detailed idea with all the strategies ?
Write 2 scenarios for Integration testing? Please let me know its urgent.
