This refers to the practice of pairing up of a developer and tester as buddies to test a piece of code or functionality. This type of testing is best applied in the early development stages after unit testing is complete and prior to checking in of the code. At this stage of product development, buddy testing may employ a variety of white and black box test techniques as appropriate to test the artifact that is available.
Buddy tests aim to avoid duplication of unit test coverage and endeavors to cover areas that may not have been addressed in unit tests, such as the user interfaces. Other important areas that buddy testing is expected to cover include, reviews of coding standards & practices, code walkthroughs, inspection and development of test scenarios to maximize coverage around statements and paths in the code. A beneficial side effect of buddy testing is greater clarity gained around product specifications which help the testers develop better tests and development to gain answers to make any needed design changes early.
Due to the early detection of issues that is possible with this type of testing, Buddy testing is often termed as "preventative" type testing where the aim is to unearth defects early in the development cycle and have them addressed when its generally cheaper to do so than in later phases. Any issues that are raised are discussed and after agreed upon changes are made, the code is checked-in. This buddy tested code is integrated and later delivered to the functional testing team by which time the specifications are clearer and there is an assurance of greater quality in the product.
Buddy Testing is the testing technique adapted under unplanned testing situations.
1. Where a Developer and Tester with work together in order to test and develop the application at a rapid pace..
2. Each will do their own job and as they work together the chance of bugs raises/fixes will be reduced so as to meet the time deadline.
Due to lack of time and lack of test data test engineers grouped with developers to conduct test on application as early as possible this style of testing. "Buddy means a group of Programmers and Testers". The management people are grouping few programmers and few testers as a buddy. Every buddy consists of programmers and testers.
Buddy tests aim to avoid duplication of unit test coverage and endeavors to cover areas that may not have been addressed in unit tests, such as the user interfaces. Other important areas that buddy testing is expected to cover include, reviews of coding standards & practices, code walkthroughs, inspection and development of test scenarios to maximize coverage around statements and paths in the code. A beneficial side effect of buddy testing is greater clarity gained around product specifications which help the testers develop better tests and development to gain answers to make any needed design changes early.
Due to the early detection of issues that is possible with this type of testing, Buddy testing is often termed as "preventative" type testing where the aim is to unearth defects early in the development cycle and have them addressed when its generally cheaper to do so than in later phases. Any issues that are raised are discussed and after agreed upon changes are made, the code is checked-in. This buddy tested code is integrated and later delivered to the functional testing team by which time the specifications are clearer and there is an assurance of greater quality in the product.
Buddy Testing is the testing technique adapted under unplanned testing situations.
1. Where a Developer and Tester with work together in order to test and develop the application at a rapid pace..
2. Each will do their own job and as they work together the chance of bugs raises/fixes will be reduced so as to meet the time deadline.
Due to lack of time and lack of test data test engineers grouped with developers to conduct test on application as early as possible this style of testing. "Buddy means a group of Programmers and Testers". The management people are grouping few programmers and few testers as a buddy. Every buddy consists of programmers and testers.
No comments:
Post a Comment