16.What is white box testing:
Ans: In white-box testing, the tester has access to the code implementation. The test cases are designed to cover the different paths and loops in the implementation. For white-box testing, some basic coding knowledge and background are an additional advantage.
17.What are the advantages of manual testing?
Ans:
1. It is more suitable for small projects
2. A tester can find more bugs when performing test cases unlike automation
3. The test cases can be easily tuned to adjust to the changes in the code and UI
4. Difficult scenarios and switching between systems and modules can be easily done
5. Very useful in ad-hoc, exploratory, and usability testing
6. Needs fewer skills and can be learned easily
18.What are the disadvantages of manual testing?
Ans: 1. It is time-consuming and not suitable for projects with strict timelines
2. It can become redundant for functionalities that are stable with no code change
3. Performance tests can not be performed manually
4. It proves more expensive in the long run.
5. With every iteration or release, the timelines keep on increasing.
6. It is prone to human errors
19.When will you choose manual testing over automation?
Ans: Under some situations, manual testing is preferred over automation, these are:
1. Bug re-testing
2. For testing cases, that need to be run only a few times for the project.
3. For Adhoc and exploratory testing.
4. For checking the user-friendliness of the application
5. While handling complex scenarios.
6. For testing cases, where some random decision-making is involved.
20.What is a testbed?
Ans: The environment for testing with the needed parameters is called a testbed. It is a digital platform that can include the OS, hardware, software, database, network, etc.
21.What is a test case?
Ans: A test case is a set of instructions that the tester is expected to perform to test functionality. A good test case can be easily understood and run by any person even if they do not have a testing background.
In simple words- Test case defines how to test.
22.What is the 80:20 rule?
Ans: The 80:20 rule states that 80% of the defects are found in 20% of the code. This is also called defect clustering.
23.What is defect cascading?
Ans: The phenomenon where one defect if left undetected, triggers multiple defects in other modules and later stages are called defect cascading. The cost of fixing this defect cascading can be high, due to the greater number of defects in the system.
24.What is outsourced testing?
Ans: Assigning the testing task to a third party or separate team within or outside the company is called outsourced testing. This is done to ensure free and unbiased testing. Sometimes it is also helpful in giving a fresh perspective to the testing activity.
25.What is bug leakage?
Ans: A bug that is missed by the testing team during the testing phase and escapes undetected to production, where it is discovered by the actual user is called leaked bug and the phenomenon is called bug leakage.
26.What is a show stopper defect?
Ans: A defect that does not allow the testing activities to proceed is called a show stopper defect. App crash on launch and login failures are examples of show stopper defects.
27.What is a hotfix?
Ans: Sometimes a build that is deployed to production would have some critical error and it would be rolled back. Now an emergency fix for the issue is released as a new patch and this build is called a hotfix.
28.Name some challenges in software testing?
Ans: Some challenges in software testing
1. Insufficient documentation or unfrozen requirements.
2. Unavailability of skilled testing resources
3. Stringent timelines
4. Unstable systems and incomplete modules are given for testing
29.What is the age of a defect?
Ans: The age of the defect is defined as the number of days between the day the defect is accepted or assigned by the development team and the day it is verified and closed by the testing team. The age of the defect can be defined in hours and days.
30.Name some best practices in software testing.
Ans: Some best practices are:
1. Start early
2. Update your test cases, and test approach frequently to identify more defects
3. Always think like the client
4. Think out of the box
5. Automate repeated tests and focus more testing on new modules
0 Comments