Black box testing Vs White box testing
Black box testing
|
White box testing
|
It is also called behavioral or functional
or opaque testing
|
It is also called structural or glass
box testing.
|
BBT is not type of testing, it is
testing strategies which does not need any knowledge of internal design of
code.
|
Derivation of test cases according to
program is used structure knowledge of the program is used to identify
additional test cases.
|
Tester has no need the knowledge of
coding and logic i.e. internal working of the code.
|
Tester has knowledge of coding and
logic i.e. internal working of the code.
|
Inputs required for BBT
1
Requirements
2
Functional specifications
3
High level design documents
4
Application black source code
|
Inputs required for WBT
1
Requirements
2
Functional specifications
3
High-level design documents
4
Application black source code
5
Detailed design document
|
Type of BBT
Graph-based testing method:
1 Equivalent partitioning
2 Boundary value analysis
3
Comparison testing
|
Type of WBT
1
Basic path testing
2
Control structure testing
|
More effective on larger units of code.
|
Less effective on larger units of code
as compared to BBT.
|
Alpha Testing:
It is conducted at the developer sight by end users. It is conducted in controlled environment.
Alpha testing is performed by a team member of software developer in the organization, to test each and every condition depending upon customers requirements and they will satisfy themselves, that software must not failure towards the client side.
Alpha testing, process continues until the system developer and the client agrees that delivered system is an acceptable implementation of the system requirement.
Beta Testing:
It is conducted at the end users site for specific period of time. Unlike alpha testing, the developer is generally not present here, during testing time. Therefore, beta test is a "live" application of the software in an environment, i.e. not controlled by developer. The end users record all problems that are encountered during beta testing and reports these to developer at regular interval. As a result of problem reported during beta tests, software engineers make and then prepare for release of software product to entire customer base.
Any kind of problem arise during testing take action to recover them and ensure that these kind of problem are not arise in future.
It involves delivering a system to a number of potential customer, who agree to use the system. They report problems to the system developer.
Post a Comment