1. How do drivers and stubs relate to manual testing?
- Drivers and stubs are a part of incremental testing.
- The two approaches used in incremental testing are: the top down and the bottom up methods.
- Drivers are used for the bottom up approach.
- Drivers are the modules that run the components that are being tested.
- A stub is used for the top down approach.
- It is a replacement of sorts for a component which is used to test a component that it calls.
- The two approaches used in incremental testing are: the top down and the bottom up methods.
- Drivers are used for the bottom up approach.
- Drivers are the modules that run the components that are being tested.
- A stub is used for the top down approach.
- It is a replacement of sorts for a component which is used to test a component that it calls.
2. Explain the following mentioned testing types?
a.) Stress testing:
- It checks the robustness of application.
- It verifies that application consistently provides satisfactory performance under unfavorable and extreme conditions. This includes - heavy user traffic, heavy process loads, irregular hardware clocking, and heavy utilization of resources.
- Stress testing is also useful in verifying the effectiveness of error handling under extreme conditions.
b.) Sanity testing:
- Sanity testing is used to ensure that multiple or conflicting functions or variables do not exist in the system.
- It verifies that the components of the application can be compiled without a problem.
- It is conducted on all parts of the application.
c.) Ad hoc testing:
- It is a type of testing that is performed without the use of planning and/or documentation.
- These tests are run only one time unless a defect is found.
- If defect is found, testing can be repeated.
- It is considered to be a part of exploratory testing.
d.) Smoke testing:
- Smoke testing covers all of the basic functionality of the application.
- It is considered as the main test for checking the functionality of the application.
- It does not test the finer details of the application.
- It checks the robustness of application.
- It verifies that application consistently provides satisfactory performance under unfavorable and extreme conditions. This includes - heavy user traffic, heavy process loads, irregular hardware clocking, and heavy utilization of resources.
- Stress testing is also useful in verifying the effectiveness of error handling under extreme conditions.
b.) Sanity testing:
- Sanity testing is used to ensure that multiple or conflicting functions or variables do not exist in the system.
- It verifies that the components of the application can be compiled without a problem.
- It is conducted on all parts of the application.
c.) Ad hoc testing:
- It is a type of testing that is performed without the use of planning and/or documentation.
- These tests are run only one time unless a defect is found.
- If defect is found, testing can be repeated.
- It is considered to be a part of exploratory testing.
d.) Smoke testing:
- Smoke testing covers all of the basic functionality of the application.
- It is considered as the main test for checking the functionality of the application.
- It does not test the finer details of the application.
visit:www.sssedu.inhttp://sssedu.in/software-testing-training-chennai.html
No comments:
Post a Comment