Software Testing & Quality - Wk8

Uploaded by

moayyadsmra

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

0% found this document useful (0 votes)

7 views

Software Testing & Quality - Wk8

Uploaded by

moayyadsmra

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

You are on page 1/ 13

Click to edit Master title style

Software Testing & Quality

H i g h e r - O r d e r Te s t i n g

1
Click to edit Master title style

Higher-Order Testing

2 2
Click to edit Master
Higher-Order Testingtitle style

1. Translate the program user’s needs into a set of

written requirements. These are the goals for the
product.
2. Translate the requirements into specific objectives by
assessing feasibility, time, and cost, resolving
conflicting requirements, and establishing priorities
and trade-offs.
3. Translate the objectives into a precise product
specification, viewing the product as a black box and
considering only its interfaces and interactions with
the end user. This description is called the external
specification.
4. If the product is a system such as an operating
system, flight-control system, database system, or
employee personnel management system, rather
than an application (e.g., compiler, payroll program,
word processor), the next process is system design.
3 3
Click to edit Master
Higher-Order Testingtitle style

5. Design the structure of the program or programs by

specifying the function of each module, the
hierarchical structure of the modules, and the
interfaces between modules.
6. Develop a precise specification that defines the
interface to, and function of, each module.
7. Translate, through one or more substeps, the module
interface specification into the source code algorithm
of each module.

4 4
Click to edit Master
Higher-Order Testingtitle style

• Requirements specify why the program is needed.

• Objectives specify what the program should do and
how well the program should do it.
• External specifications define the exact representation
of the program to users.
• Documentation associated with the subsequent
processes specifies, in increasing levels of detail, how
the program is constructed.

5 5
Click to edit Master
Higher-Order Testingtitle style

• Three complementary approaches:

1. Introduce more precision into the
development process;
2. Introduce a separate verification step at
the end of each phase;
3. Focus each testing process on a particular
translation step.
• The need for higher-order testing
increases along with the size of the
program.
• Function testing is normally a black-box
activity.

6 6
Click to Testing
System edit Master title style

• In terms of the product, the number of errors made,

and the severity of those errors, the objectives to
specifications step in the development cycle usually is
the most error prone.
• Design the system test by analyzing the objectives;
formulate test cases by analyzing the user
documentation.

7 7
Click to Testing
System edit Master title style

• The most economical way of

conducting a system test
(economical in terms of
finding the most errors with a
given amount of money, or
spending less money to find
the same number of errors), is
to subcontract the test to a
separate company

8 8
ClickPlanning
Test to edit Master
and Control
title style

1. Objectives. The objectives of each testing phase must

be defined.
2. Completion criteria. Criteria must be designed to
specify when each testing phase will be judged to be
complete.
3. Schedules. Calendar time schedules are needed for
each phase. They should indicate when test cases will
be designed, written, and executed.
4. Responsibilities. For each phase, the people who will
design, write, execute, and verify test cases, and the
people who will repair discovered errors, should be
identified. And, because in large projects disputes
inevitably arise over whether particular test results
represent errors, an arbitrator should be identified.
5. Test case libraries and standards. In a large project,
systematic methods of identifying, writing, and 9 9

storing test cases are necessary.

ClickPlanning
Test to edit Master
and Control
title style

6. Tools. The required test tools must be identified,

including a plan for who will develop or acquire
them, how they will be used, and when they will be
needed.
7. Computer time. This is a plan for the amount of
computer time needed for each testing phase. It
would include servers used for compiling applications,
if required; desktop machines required for
installation testing; Web servers for Web-based
applications; networked devices, if required; and so
forth.
8. Hardware configuration. If special hardware
configurations or devices are needed, a plan is
required that describes the requirements, how they
will be met, and when they will be needed.
9. Integration. Part of the test plan is a definition of
how the program will be pieced together (e.g.,
1010
ClickPlanning
Test to edit Master
and Control
title style

10.Tracking procedures. You must identify means to

track various aspects of the testing progress,
including the location of error-prone modules and
estimation of progress with respect to the schedule,
resources, and completion criteria.
11.Debugging procedures. You must define mechanisms
for reporting detected errors, tracking the progress
of corrections, and adding the corrections to the
system. Schedules, responsibilities, tools, and
computer time/resources also must be part of the
debugging plan.
12.Regression testing. Regression testing is performed
after making a functional improvement or repair to
the program. Its purpose is to determine whether
the change has regressed other aspects of the
program. It usually is performed by rerunning some
subset of the program’s test cases. 1111
Click to
Final Report
edit Master title style

• Choose a paper on test automation and send me a copy before 12/1

• Prepare a 12-mins talk & a 8-mins QA session
• Literature review
• Algorithm & experimental results
• You should be able to explain the technical details of the paper you
choose