QTP Questions
- Difference between Black box testing and White box testing
A. Black box testing: Not based on any knowledge of internal design or code. Tests are based on requirements and functionality.
White box testing: Based on knowledge of the internal logic of an application's code. Tests are based on coverage of code statements, branches, paths, conditions.
- What is Unit Testing?
A.The most 'micro' scale of testing; to test particular functions or code modules. Typically done by the programmer and not by testers, as it requires detailed knowledge of the internal program design and code. Not always easily done unless the application has a well designed architecture with tight code; may require developing test driver modules or test harnesses.
- What is Integration testing?
A.Testing of combined parts of an application to determine if they function together correctly. The 'parts' can be code modules, individual applications, client and server applications on a network, etc. This type of testing is especially relevant to client/server and distributed systems.
- What is Incremental integration testing?
A. Continuous testing of an application as new functionality is added; requires that various aspects of an application's functionality be independent enough to work separately before all parts of the program are completed, or that test drivers be developed as needed; done by programmers or by testers.
- What is Functional testing?
A. Blackbox type testing geared to functional requirements of an application; this type of testing should be done by testers. This doesn't mean that the programmers shouldn't check that their code works before releasing it (which of course applies to any stage of testing.).
- What is System testing?
A. Blackbox type testing that is based on overall requirement specifications; covers all combined parts of a system.
- What is End to end testing?
A. Similar to system testing; the 'macro' end of the test scale; involves testing of a complete application environment in a situation that mimics real world use, such as interacting with a database, using network communications, or interacting with other hardware, applications, or systems if appropriate.
- What is Sanity testing?
A. Typically an initial testing effort to determine if a new software version is performing well enough to accept it for a major testing effort. For example, if the new software is crashing systems every 5 minutes, bogging down systems to a crawl, or destroying databases, the software may not be in a 'sane' enough condition to warrant further testing in its current state.
- What is Regression testing?
A. Retesting after fixes or modifications of the software or its environment.
It can be difficult to determine how much retesting is needed, especially near the end of
the development cycle. Automated testing tools can be especially useful for this type of testing.
- What is Acceptance testing?
A. Final testing based on specifications of the end user or customer, or based on
use by end users/customers over some limited period of time.
- What is Load testing?
A. Testing an application under heavy loads, such as testing of a web site under
a range of loads to determine at what point the systems response time degrades or fails.
- What is Stress testing?
A. Term often used interchangeably with 'load' and 'performance' testing. Also used
to describe such tests as system functional testing while under unusually heavy loads, heavy
repetition of certain actions or inputs, input of large numerical values, large complex
queries to a database system, etc.
- What is Performance testing?
A. Term often used interchangeably with 'stress' and 'load' testing. Ideally 'performance'
testing (and any other 'type' of testing) is defined in requirements documentation or QA or Test Plans.
