Summary of Previous Lecture - 13

Software Testing
Principles of Testing
Software Testing Lifecycle
Software Testing Activities
Role of Tester
Skills of Tester
Testing Methods
SQA Team

1 12/25/2021
 Today’s Lecture - 14

1. Testing Stages
2. Test Cases
3. Testing Types

2 12/25/2021
 Stages of Testing
Unit testing/Component Testing/Module testing[2,3,6]
Integration Testing
System testing
Acceptance testing • An over-seas review might take
many days as each ―back and
forth‖ can take a day, so it might
take five days to complete a review
instead of thirty minutes.
• It is difficult for Project managers
to track whether all changes have
been reviewed

3 12/25/2021
 Test Case
A test case in software engineering is a set of conditions or variables under
which a tester will determine whether an application or software system
meets specifications.
A test case has components that describes an input, action or event and an
expected response, to determine if a feature of an application is working
correctly.
The mechanism for determining whether a software program or system
has passed or failed such a test is known as a test oracle.
Test Suite: A collection of test cases.
A test case may include many subsets.

4 12/25/2021
 Test Case
Test Case ID: It is unique number given to test case in order to be
identified.
Test description: The description of test case you are going to test.
Revision history: Each test case has to have its revision history in order to
know when and by whom it is created or modified.
Function to be tested: The name of function to be tested.
Test Setup: Anything you need to set up outside of your application for
example printers, network and so on.

5 12/25/2021
 Test Case
Test Execution: It is detailed description of every step of execution.
Expected Results: The description of what you expect the function to do.
Actual Results: pass / failed
 If pass - What actually happen when you run the test.
 If failed - put in description of what you've observed.

6 12/25/2021
 Test Case
 Test case for login creation? User name must be of type character and password must be
minimum of Case
lengthTest
6.case Test Execution Expected Pass/ Remarks
# Results Fail

Login Enter abcdef in user name Login page

1 creation field created
Enter the password, length
of 6 or more
Enter the same password
in confirm password field
Press enter
2 Enter abcdef in user name Error Validator
field message if check
Enter the password, length check is should be
of 6 or more there for visible
Enter some other confirm suggesting
password in confirm password that
password field passwords
Press enter not
matched
7 12/25/2021
 Traceability Matrix
Traceability Matrix is a document used for tracking the requirement, test
cases and the defects
This document is made to convince the client that the coverage done is
complete as end to end
This document contains Requirement id, test case condition and bug id
Using this document the person can track the requirement based on bug id

8 12/25/2021
 High Level vs Low Level Test Case
High Level Test Case Low Level Test Case
High Level Test cases cover the whole Low level test cases cover each and
application in a broader way. They do every individual units of code and test
not cover the functionalities in detail cases are generated to test each and
but the overall application should every unit in depth
work fine

Abstract More Detailed

9 12/25/2021
 Testing Types
Black Box Testing
White Box Testing
Gray Box Testing

10 12/25/2021
 Black Box Testing
 In science and engineering, a black box is a device, system or object which can be viewed solely in terms
of its input, output and transfer characteristics without any knowledge of its internal workings, that is, its
implementation is "opaque" (black).
 Also known as functional testing. A software testing technique whereby the internal workings of the item
being tested are not known by the tester. For example, in a black box test on a software design the tester
only knows the inputs and what the expected outcomes should be and not how the program arrives at those
outputs. The tester does not ever examine the programming code and does not need any further knowledge
of the program other than its specifications.

11 12/25/2021
 Black Box Testing

• Tester can be non-technical. • Chances of having repetition of

• This testing is most likely to find tests that are already done by
those bugs as the user would programmer.
find. • It is difficult to identify all
• Testing helps to identify the possible inputs in limited testing
contradiction in functional time.
specifications.
• Test cases can be designed as
soon as the functional
specifications are complete.

12 12/25/2021
 White-Box Testing
 White-box testing (also known as clear box
testing, glass box testing, transparent box
testing, and structural testing) is a method of
testing software that tests internal structures or
workings of an application, as opposed to its
functionality (i.e. black-box testing).
 The connotations of “clear box” and “glass box”
appropriately indicate that you have full visibility
of the internal workings of the software product,
specifically, the logic and the structure of the
code.
 In white-box testing an internal perspective of the
system, as well as programming skills, are
required and used to design test cases. The tester
chooses inputs to exercise paths through the code
and determine the appropriate outputs.
13 12/25/2021
 White-Box Testing

• As the knowledge of internal • As knowledge of code and

coding structure is prerequisite, internal structure is a
it becomes very easy to find out prerequisite, a skilled tester is
which type of input/data can needed to carry out this type of
help in testing the application testing..
effectively.
• The other advantage of white
box testing is that it helps in
optimizing the code

14 12/25/2021
 Gray Box Testing
Gray box testing is a software testing technique that uses a combination of
black box testing and white box testing. Gray box testing is not black box
testing, because the tester does know some of the internal workings of the
software under test.
In gray box testing, the tester applies a limited number of test cases to the
internal workings of the software under test. In the remaining part of the
gray box testing, one takes a black box approach in applying inputs to the
software under test and observing the outputs.
This is particularly important when conducting integration testing between
two modules of code written by two different developers, where only the
interfaces are exposed for test.
15 12/25/2021
 References
Software Engineering by Roger Pressman
http://jamesmccaffrey.wordpress.com/2008/08/29/the-difference-between-unit-testing-and-module-testing/
http://www.faqs.org/faqs/software-eng/testing-faq/section-14.html
http://en.wikipedia.org/wiki/White-box_testing
http://agile.csc.ncsu.edu/SEMaterials/WhiteBox.pdf
http://blogs.ebusinessware.com/2009/06/26/unit-testing-vs-module-testing/
John Watkins ,”Testing IT”, 2001, Cambridge University Press
http://chamaras.blogspot.com/2008/08/what-is-software-testing-life-cycle.html
GlenFord Myers, “The Art of Software Testing” 2nd Edition
http://softwaretestingguide.blogspot.com/2007/08/explain-traceability-matrix_30.html
http://www.onestoptesting.com
http://www.softwaretestingmentor.com/automation/manual-vs-automation.php

16 12/25/2021