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
What is boundary value testing? Give an example.
What is Application Performance testing and Operational performance testing
HI GUYS,, I HAVE 3 YEARS OF EXP IN MANUAL TESTING...NEXT MONTH ONWARDS I WORK FOR MOBILE TESTING....PLS SUGGEST ME WHAT I LEARN FOR TRAING,, MOBILE TESTING OR ANDROID....FOR MOBILE TESTERS NEED ANDROID(IFONE) DEVOLOPMENT KNOWLEDGE OR NOT? EXPLAIN CLEARLY
Explain what is exhaustive testing?
How will you determine when to stop testing?
1.Enlist the types of testing performed for any window in sequence? 2.Use of edit_get_list function 3.Accuracy & Precision
What is system level testing?
Can you explain requirement traceability and its importance?
What is state transition?
Scenario-based testing Option 1 concentrates on actor and software interaction Option 2 misses errors in specifications Option 3 misses errors in subsystem interactions Option 4 Both 1 abd 2
What is an error?
Can you do system testing at any stage of sdlc?
Why would we not include these?
whar are the contents in db testing test case template
Which are the different tests for apparel testing?