Topic: Black Box Testing Techniques

Message


   Black Box Testing Techniques
Equivalence Partitioning
Boundary Value Analysis
State Transitions
Exploratory Testing
1) Equivalence Partitioning
       Partition the input domain into a finite number of equivalence classes
       Create test cases to invoke as many different conditions as possible

It is based on the premise that if a test case in an equivalence class
detects an error, all other test cases in the same class detect the
same error
Step 1
           Identify the input parameters
           Identify the allowable classes of input
           Select a representative value for each class
           Create test cases to cover as many classes as possible
Step 2
           Select invalid values for each class
           Create additional test cases to cover invalid classes
Step 3
          Identify the output parameters
          Identify the possible classes of output
          Create test cases to generate each possible output

Example:
                Strategy:
                     •Identify input equivalence classes
                             –Based on conditions on inputs / outputs in specification / description
                             –Both valid and invalid input equivalence classes
                             –Based on heuristics and experience
                    •“Input x in [1..10]”        ® classes: x <> 10
                    •“Enumeration A, B, C    ® classes:  A, B, C, not {A, B, C,}
                    • Define one / couple of test cases for each class
                             –Test cases that cover valid eq. classes
                             –Test cases that cover at most one invalid eq. class
                    •Test a function for calculation of absolute value of an integer
                    •Equivalence classes :
2) Boundary Value Analysis
Boundary Value Analysis technique tests conditions on, above and beneath the edges of input and output Equivalence Classes
Test cases are created to test the edge of each Equivalence Class
Test cases are created to test edges of both input and output classes
For each equivalence class identified:
Select a value on the class boundary
Pick a value just under the boundary
Pick a value just over the boundary
3) Finite State Testing Process:
Create test cases to:
Force each transition
Force each action
4) Exploratory Testing
Some people can design test cases that will discover failures based on their experience
Allow these people to write test cases
Address complex areas
Address changes
Report failures, faults and errors so that experience level may grow

Author	Message
tanushree Senior Member Joined: 04Apr2007 Online Status: Offline Posts: 2160	Topic: Black Box Testing Techniques Posted: 01Aug2007 at 6:38am
	*Black Box Testing Techniques* Equivalence Partitioning Boundary Value Analysis State Transitions Exploratory Testing 1) Equivalence Partitioning Partition the input domain into a finite number of equivalence classes Create test cases to invoke as many different conditions as possible It is based on the premise that if a test case in an equivalence class detects an error, all other test cases in the same class detect the same error Step 1 Identify the input parameters Identify the allowable classes of input Select a representative value for each class Create test cases to cover as many classes as possible Step 2 Select invalid values for each class Create additional test cases to cover invalid classes Step 3 Identify the output parameters Identify the possible classes of output Create test cases to generate each possible output Example: Strategy: •Identify input equivalence classes –Based on conditions on inputs / outputs in specification / description –Both valid and invalid input equivalence classes –Based on heuristics and experience •“Input x in [1..10]” ® classes: x <> 10 •“Enumeration A, B, C ® classes: A, B, C, not {A, B, C,} • Define one / couple of test cases for each class –Test cases that cover valid eq. classes –Test cases that cover at most one invalid eq. class •Test a function for calculation of absolute value of an integer •Equivalence classes : 2) Boundary Value Analysis Boundary Value Analysis technique tests conditions on, above and beneath the edges of input and output Equivalence Classes Test cases are created to test the edge of each Equivalence Class Test cases are created to test edges of both input and output classes For each equivalence class identified: Select a value on the class boundary Pick a value just under the boundary Pick a value just over the boundary 3) Finite State Testing Process: Create test cases to: Force each transition Force each action 4) Exploratory Testing Some people can design test cases that will discover failures based on their experience Allow these people to write test cases Address complex areas Address changes Report failures, faults and errors so that experience level may grow Post Resume: Click here to Upload your Resume & Apply for Jobs

	IP Logged

anandamalan Newbie Joined: 31Jul2007 Location: India Online Status: Offline Posts: 1	Posted: 02Aug2007 at 11:02pm
	Good and fantastic Post Tanushree, Keep it up. Anand Amalan
	IP Logged

sairevathi Newbie Joined: 25Sep2008 Location: India Online Status: Offline Posts: 34	Posted: 29Sep2008 at 4:24am
	1)Equivalence Partitioning 2)Boundary Value Analysis 3)Error guessing
	IP Logged

tossy Groupie Joined: 20Aug2008 Online Status: Offline Posts: 99	Posted: 17Oct2008 at 3:13am
	Black box testing is a testing that mainly concentrate on the functional department of a software program.Black box testing is complementry to white box testing.black box testing deals with the external view of the program.In this testing, test case don't know about the internal structure of the program.Black box testing starts when the white box testing stops.The black box testing is mainly done by programmer of every level in one or the other way. Suppose,we have a program of finding the greatest out of three numbers.For this, black box testing will be as follows:-- 1)What are the required inputs for this program? lets say----4,6,3 2)The output for this will be 6. 3)Now if the answer is 6, then the program is O.K otherwise, the program is wrong. Black Box testing techniques. Equivalence Partitioning Method Boundary Value Analysis Decision tables Cause Effect Graphing State Transition Testing Orthogonal Array testing Strategy (OATS) technique Edited by tossy - 17Oct2008 at 3:14am

	IP Logged

qualitypoint Groupie Joined: 12May2009 Online Status: Offline Posts: 45	Posted: 15May2009 at 5:38am
	you can see the steps for writing good test cases here. http://qualitypoint.blogspot.com/2009/05/writing-good-test-cases-and-finding.html
	IP Logged


One Stop Testing Forum : Software Testing @ OneStopTesting : Beginners @ OneStopTesting