8/3/2019 05-Aug- Unit2 Part 1
1/14
Software Testing and Quality Assurance
(Elective)
Unit 2
Session 1
Rajesh Singh
04-Aug-2011
Software Testing and Quality Assurance (Elective II 410445) Unit 2
8/3/2019 05-Aug- Unit2 Part 1
2/14
Topics to be covered in this session:
1) Introduction2) Need of Black Box Testing
3) Black box testing Concept
4) Requirement Analysis
5) Summary
Software Testing and Quality Assurance (Elective II 410445) Unit 2
8/3/2019 05-Aug- Unit2 Part 1
3/14
Introduction
Software Testing and Quality Assurance (Elective II 410445 ) Unit 2
Test-to-Pass and Test-to-Fail
There are two fundamental approaches to testing software: test-to-pass and test-to-fail.
When you test-to-pass, you really assure only that the software minimally works. You
don't push its capabilities. You don't see what you can do to break it. You treat it with kid
gloves, applying the simplest and most straightforward test cases.
You may be thinking that if your goal is to find bugs, why would you test-to-pass?
Wouldn't you want to find bugs by any means possible? The answer is no, not initially.
Think about an analogy with a newly designed car .You're assigned to test the very first
prototype that has just rolled off the assembly line and has never been driven. You
probably wouldn't get in, start it up, head for the test track, and run it wide open at full
speed as hard as you could. You'd probably crash and die. With a new car, there'd be all
kinds of bugs that would reveal themselves at low speed under normal driving conditions.
Maybe the tires aren't the right size, or the brakes are inadequate, or the engine is too
loud. You could discover these problems and have them fixed before getting on the track
and pushing the limits.
8/3/2019 05-Aug- Unit2 Part 1
4/14
Introduction
Software Testing and Quality Assurance (Elective II 410445 ) Unit 2
Black Box and White Box testing
Black-box and white-box are test design methods.
Black-box test design treats the system as a "black-box", so it doesn't explicitly use
knowledge of the internal structure. Black-box test design is usually described as
focusing on testing functional requirements. Synonyms for black-box include: behavioral,
functional, opaque-box, and closed-box.
White-box test design allows one to peek inside the "box", and it focuses specifically on
using internal knowledge of the software to guide the selection of test data. Synonyms for
white-box include: structural, glass-box and clear-box.
8/3/2019 05-Aug- Unit2 Part 1
5/14
Introduction
Software Testing and Quality Assurance (Elective II 410445 ) Unit 2
Black Box and White Box testing
While black-box and white-box are terms that are still in popular use, many people
prefer the terms "behavioral" and "structural". Behavioral test design is slightly
different from black-box test design because the use of internal knowledge isn't strictly
forbidden, but it's still discouraged. In practice, it hasn't proven useful to use a single
test design method. One has to use a mixture of different methods so that they aren't
hindered by the limitations of a particular one.
It is important to understand that these methods are used during the test design
phase, and their influence is hard to see in the tests once they're implemented. Note
that any level of testing (unit testing, system testing, etc.) can use any test design
methods. Unit testing is usually associated with structural test design, but this is
because testers usually don't have well-defined requirements at the unit level to
validate.
8/3/2019 05-Aug- Unit2 Part 1
6/14
Software Testing and Quality Assurance (Elective II 410445) Unit 2
Need of Black Box Testing
What is black box testing?
Knows only what the software is supposed to doDoesnt know how it operates inside
Why named as black box testing?
You cannot see inside the box
8/3/2019 05-Aug- Unit2 Part 1
7/14
Software Testing and Quality Assurance (Elective II 410445) Unit 2
Need of Black Box Testing
Black-box: There are many advantages to black-box testing. Here are a few of the
most commonly cited:
1. Ease of use. Because testers do not have to concern themselves with the inner
workings of an application, it is easier to create test cases by simply working
through the application, as would an end user.
2. It can be performed by non technical users also such as dummy users who do not
have programming or testing knowledge
3. Quicker test case development. Because testers only concern themselves with
the GUI, they do not need to spend time identifying all of the internal paths that
may be involved in a specific process, they need only concern themselves with
the various paths through the GUI that a user may take
4. Simplicity. Where large, highly complex applications or systems exist black-boxtesting offers a means of simplifying the testing process by focusing on valid and
invalid inputs and ensuring the correct outputs are received.
5. Actual Users can do Black Box Testing methods and understand the results.
8/3/2019 05-Aug- Unit2 Part 1
8/14
Software Testing and Quality Assurance (Elective II 410445) Unit 2
Black Box Testing Concept
Black box testing treats the system as a black-box, so it doesnt explicitly use
Knowledge of the internal structure or code. Or in other words the Test engineer neednot know the internal working of the Black box or application.
Main focus in black box testing is on functionality of the system as a whole.
8/3/2019 05-Aug- Unit2 Part 1
9/14
Software Testing and Quality Assurance (Elective II 410445) Unit 2
Black Box Testing Concept
Focus on input and output of the software without regard to the internal code
of the program
8/3/2019 05-Aug- Unit2 Part 1
10/14
Software Testing and Quality Assurance (Elective II 410445) Unit 2
Black Box Testing Concept
8/3/2019 05-Aug- Unit2 Part 1
11/14
Software Testing and Quality Assurance (Elective II 410445) Unit 2
Tests of Customer Requirements
As part of Black Box testing the basic strategy is to do the requirementanalysis and go through the requirement specification to perform a Black Box
testing to check if customers requirements are present and working.
Have two paths:
success path.
failure path.
risky requirements should tested first
8/3/2019 05-Aug- Unit2 Part 1
12/14
SummaryToday we have gone through following Topics:
1) Introduction
2) Need of Black Box Testing3) Black box testing Concept4) Requirement Analysis
In next Session following Topics will be picked up:-
Unit 2 Further details on Black Box testing
Software Testing and Quality Assurance (Elective II 410445) Unit 2
8/3/2019 05-Aug- Unit2 Part 1
13/14
Any Question/Query???
Software Testing and Quality Assurance (Elective II 410445) Unit 2
8/3/2019 05-Aug- Unit2 Part 1
14/14
Thank You for your Patience!!
If you need some more information you
can drop me an email [email protected]
Software Testing and Quality Assurance (Elective II 410445) Unit 2