12. Types of Risks & Solutions

12. Types of risks & its Solutions:
The types of risk the tester will face during the testing the applications are
Due to lack of time (Buddy Testing).
Due to lack of Documentation (Exploratory testing).
Due to lack of Domain Knowledge (Pair testing).

12.1. Buddy Testing (Due to lack of time):
Buddy means group of programmers & testers. In this kind of testing, the coding and testing processes are going on parallely due to lack time for testing (i.e.) as the develop the programs to develop the functionality, parallely it will be tested by the tester.
(Or)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 group of programmers and testers".
(Or)Buddy Testing is the testing technique adapted under unplanned testing situations...Where a Developer and Tester with work together in order to test and develop the application at a rapid pace. Each will do their own job and as they work together the chance of bug’s raises/fixes will be reduced so as to meet the time deadline.

12.2. Exploratory Testing (Due to lack of Documentation):
Due to lack of documentation, the testing team is depending on available documents, discussions with other in a testing team, internet browsing, previous experience to understand the customer requirements, contacting the client or customer who specifies the requirement.
(Or)
Its a kind of testing conducting at the time of documentation lacking. In the testing process whenever we don’t have sufficient documentation to do the testing process like preparing test scenarios, test cases then we will go for the following
Techniques.
1) Getting information from the previous projects
2) Taking suggestions from the seniors and leads or managers

12.3. Pair Testing (Due to lack of Domain knowledge):
Due to lack of lack of domain knowledge, the test lead is defining pairs with a senior test engineer & a junior test Engineer to share their knowledge during testing. Pair means a senior test engineer, a junior test engineer. Lack of domain knowledge for test engineer in a testing team means no training sessions are provided for them to understand the development project.