1.What different testing approaches are in Software Testing?
A: Each of the followings represents a different testing approach:
1.Black box testing
2. White box testing
3. Unit testing
4. Incremental testing
5. Integration testing
6. Functional testing
7. System testing
8. End-to-end testing
9. Sanity testing
10. Regression testing
11. Acceptance testing
12. Load testing
13. Performance testing
14. Usability testing
15. Install/uninstall testing
16. Recovery testing
17. Security testing
18. Compatibility testing
19. Exploratory testing
20. Ad-hoc testing
21. User acceptance testing
22. Comparison testing
23. Alpha testing
24. Beta testing
25. Mutation testing.
2. What is glass box testing in Software Testing?
A: Glass box testing is the same as white box testing. It is a testing approach that examines the application's program structure, and derives test cases from the application's program logic.
3. What is open box testing in Software Testing?
A: Open box testing is same as white box testing. It is a testing approach that examines the application's program structure, and derives test cases from the application's program logic.
4.What is black box testing in Software Testing?
A: Black box testing a type of testing that considers only externally visible behavior. Black box testing considers neither the code itself, nor the "inner workings" of the software. You CAN learn to do black box testing, with little or no outside help. Get CAN get free information. Click on a link!
5. What is unit testing in Software Testing?
A: Unit testing is the first level of dynamic testing and is first the responsibility of developers and then that of the test engineers. Unit testing is performed after the expected test results are met or differences are explainable/acceptable.
6. What is system testing in Software Testing?
A: System testing is black box testing, performed by the Test Team, and at the start of the system testing the complete system is configured in a controlled environment. The purpose of system testing is to validate an application's accuracy and completeness in performing the functions as designed. System testing simulates real life scenarios that occur in a "simulated real life" test environment and test all functions of the system that are required in real life. System testing is deemed complete when actual results and expected results are either in line or differences are explainable or acceptable, based on client input. Upon completion of integration testing, system testing is started. Before system testing, all unit and integration test results are reviewed by Software QA to ensure all problems have been resolved. For a higher level of testing it is important to understand unresolved problems that originate at unit and integration test levels.
7. What is parallel/audit testing in Software Testing?
A: Parallel/audit testing is testing where the user reconciles the output of the new system to the output of the current system to verify the new system performs the operations correctly.
With parallel testing, users can easily choose to run batch tests or asynchronous tests depending on the needs of their test systems. Testing multiple units in parallel increases test throughput and lower a manufacturer's
8. What is functional testing in Software Testing?
A: Functional testing is black-box type of testing geared to functional requirements of an application. Test engineers *should* perform functional testing.
9. What is usability testing in Software Testing?
A: Usability testing is testing for 'user-friendliness'. Clearly this is subjective and depends on the targeted end-user or customer. User interviews, surveys, video recording of user sessions and other techniques can be used. Programmers and developers are usually not appropriate as usability testers.
10. What is integration testing in Software Testing?
A: Upon completion of unit testing, integration testing begins. Integration testing is black box testing. The purpose of integration testing is to ensure distinct components of the application still work in accordance to customer requirements. Test cases are developed with the express purpose of exercising the interfaces between the components. This activity is carried out by the test team.
Integration testing is considered complete, when actual results and expected results are either in line or differences are explainable/acceptable based on client input.