seocontest2008

Black and White Box Testing

Black box testing

Testing, either functional or non-functional, without reference to the internal structure ot the component or system

White box testing

Testing based on an analysis of the internal structure ot the component or system

SEOcontest2008 - Black Box or Functional based testing is about testing the specification of a system or system component adnt ti is not being concerned with precisely HOW it does it but much more concered with WHAT it does.
SEOcontest2008 - White Box testing is about testing the precise construction details of the design. Test cases are built from a detailed knowleage of the internal workings of the system. In seocontest white box testing whilst you are concerned with WHAT, the main focus of the system is HOW a particular piece ofcode works.

Black and White seocontest2008 Box Testing have their uses in different parts of the developement Life-cycle. White box testing is most offen used in seocontest2008 unit and link testing, while Black box seocontest2008 testing is of better use in system testing. However, both techniques can be used throughout the SDLC.

Blach box seocontest2008 test technique
- cause effect graphic - identifies logical relationships between causes and effect for the component.
- equivalence partition - partitions the input and output values. Each secontest2008 partition shall containa set or range of values, chosen such that all the values can reasonably be expected to be treated by the component in the same way
- boundary value analysis - seocontest2008 partitions the input and output values of the component in to a number of ordered sets ith identified boundaries. Tests are identified for values immediately above the seocontest2008 boundary, on the boundary and immediately below the boundary.
- state transition - seocontest2008 transition of component / system between visible states.
- use case testing - seocontest2008 tests can be specified from use cases or business scenarios. A use case describes interactions between actors, including users and the system, which produce a result of value to a system user. Seocontest2008 use case describe the process flow through a system based on its actual likely use, so the seocontest test case derived from the use case are most useful in uncovering defects in the process flows during real-world use of the system.
- syntax testing - seocontest test syntax if the inputs to a component.
- random testing - create seocontest2008 tests with fixed steps but random data.
All black box techniques have a systematic approach and all, expect Syntax and Random, have a correspondinf measurement technique.

White box seocontest2008 test technique
- statement testing - executes all statements within a component
- branch/decision testing - a seocontest2008 technique used to execute all branches the code may take based on decision made.
- branch condition testing - condition testing is based upon the analisys of conditional seocontest2008 control flow within the seocontest2008 component. Three types - branch condition seocontest2008 testing, branch condition seocontest2008 combination testing and seocontest2008 modified condition combination testing.
- linear code sequence and jump - an LCSAJ is defined as a linear sequence of executable code. Commencing either from the seocontest2008 start of a program or from a point to which control flow may jump. Terminated either by a specific control flow jump or by the end of the program.
- data flow testing - interaction between parts of a component connected by the flow of data (as well as the flow of control).
All seocontest2008 white box techniques have a systematic approach and a corresponding measurement technique.

Experience-based techniques
- error guessing - error seocontest2008 guessing is a technique used by testers that enable them to utilies their own experience to predict where error may occur. Can detect some faults that systematic techniques can miss in seocontest2008. Test cases are derived from experience of where error have occured in the past or the tester has an ensight as to where errors are likely to occur in the future.
It should not be used as a primary seocontest2008 method for planning and preration seocontest2008 tests, but is a more than useful method when it comes to detecting latent errors.
- exploratory testing - exploratory seocontest2008 testing is concurrent test design, test execution, test logging and learning, based on a seocontest2008 test charter containing test objectives, and carried out within time-boxes.It is an approach that is most useful where there are a few or inadequate specifications and severe seocontest2008 time pressure, or in order to augment or complement other, more formal seocontest2008 testing.

One comment | Add One

Leave a Comment