Presentation On TESTING LEVELS
Download
TESTING LEVELS Presentation Transcript:
1.TESTING LEVELS
2.Black box testing focuses on software external attributes and behavior. Such testing looks at an application’s expected behaviour from the users point.
White box testing/glass-box testing, however, tests software with knowledge of internal data structures, physical logic, flow, and architecture at the source code level.
White box testing looks at testing from the developer’s point of view.
Both black-box and white- box testing are critically important complements of a complete testing effort.
Individually, they do not allow for balanced testing. Black box testing can be less effective at uncovering certain error types as data- flow errors or boundary condition errors at the source level. White box testing does not readily highlight macro level quality risks in operating environmental comp ability, time-related errors and usability.
3.When we talk of levels of testing then we are actually talking of three levels of testing:
(a) Unit Testing
(b) Integration Testing, and
(c) System Testing
Generally, system testing is functional rather than structural testing, we shall now study these testing techniques one by one.
4.Unit testing – “is the process of taking a module and running it in isolation from the rest of the software product by using prepared test cases and comparing the actual results with the results predicted by the specification and design module.”
5.A system is composed of multiple components or modules that comprise hardware and software. Integration is defined as the set of interactions among components. Testing the interaction between the modules and interaction with other systems externally is called as integration testing.
It is both a type of testing and a phase of testing. The architecture and design can give the details of interaction within systems. However, testing the interaction between one system and integration depends on many modules and system. This ensuing phase is called the integration testing phase.
6.Classification of Integration Testing
7.The goal of decomposition based integration is to test the interfaces among separately tested units.
Types of decomposition based techniques Top-Down integration Approach
Bottom Up Integration Approach
Sandwich Integration Approach
Big Bang Strategy
Pros and cons of decomposition Based Techniques
Guidelines to choose integration Method and conclusions
8.One of the drawbacks of decomposition-based integration is that the basis is the functional decomposition tree. But if we use call graph based technique instead, we can remove this problem.
Also, we will move in the direction of structural testing. Because call graph is a directed graph and thus we can use it as a program graph also.
9.Pairwise Integration
The main idea behind pairwise integration is to eliminate the stub/driver development effort. The end result is what we have one integration test session for each edge in the call graph.
Neighborhood Integration
The neighbourhood of a node in a graph is the set of nodes that are one edge away from the given node.
10.Pros and cons
the call graph based integration techniques move away from a purely structural basis toward behavioral matches well with the developments characterized by builds.
Download
TESTING LEVELS Presentation Transcript:
1.TESTING LEVELS
2.Black box testing focuses on software external attributes and behavior. Such testing looks at an application’s expected behaviour from the users point.
White box testing/glass-box testing, however, tests software with knowledge of internal data structures, physical logic, flow, and architecture at the source code level.
White box testing looks at testing from the developer’s point of view.
Both black-box and white- box testing are critically important complements of a complete testing effort.
Individually, they do not allow for balanced testing. Black box testing can be less effective at uncovering certain error types as data- flow errors or boundary condition errors at the source level. White box testing does not readily highlight macro level quality risks in operating environmental comp ability, time-related errors and usability.
3.When we talk of levels of testing then we are actually talking of three levels of testing:
(a) Unit Testing
(b) Integration Testing, and
(c) System Testing
Generally, system testing is functional rather than structural testing, we shall now study these testing techniques one by one.
4.Unit testing – “is the process of taking a module and running it in isolation from the rest of the software product by using prepared test cases and comparing the actual results with the results predicted by the specification and design module.”
5.A system is composed of multiple components or modules that comprise hardware and software. Integration is defined as the set of interactions among components. Testing the interaction between the modules and interaction with other systems externally is called as integration testing.
It is both a type of testing and a phase of testing. The architecture and design can give the details of interaction within systems. However, testing the interaction between one system and integration depends on many modules and system. This ensuing phase is called the integration testing phase.
6.Classification of Integration Testing
7.The goal of decomposition based integration is to test the interfaces among separately tested units.
Types of decomposition based techniques Top-Down integration Approach
Bottom Up Integration Approach
Sandwich Integration Approach
Big Bang Strategy
Pros and cons of decomposition Based Techniques
Guidelines to choose integration Method and conclusions
8.One of the drawbacks of decomposition-based integration is that the basis is the functional decomposition tree. But if we use call graph based technique instead, we can remove this problem.
Also, we will move in the direction of structural testing. Because call graph is a directed graph and thus we can use it as a program graph also.
9.Pairwise Integration
The main idea behind pairwise integration is to eliminate the stub/driver development effort. The end result is what we have one integration test session for each edge in the call graph.
Neighborhood Integration
The neighbourhood of a node in a graph is the set of nodes that are one edge away from the given node.
10.Pros and cons
the call graph based integration techniques move away from a purely structural basis toward behavioral matches well with the developments characterized by builds.
No comments:
Post a Comment