Lect7 2

Download as ppt, pdf, or txt
Download as ppt, pdf, or txt
You are on page 1of 17

FUNDAMENTALS OF SOFTWARE

TESTING
SYSTEM TEST PHASE

Objective of the System Test Phase


In this test phase, product features are fully tested as well
as system-wide capabilities as a production-like. The tests
are focused on ensuring that the system operates in conformity
with the product and feature specifications.

2
SYSTEM TEST RELATED ACTIVITIES
Participate in reviews of Product and
Feature Specifications, and High Level
Design Documents

Write System Test Plan & Test Cases

System Test Plan & Test Case Review

How many
System Test System Test Report / System Handover
related activities (Verification Acceptance Meeting) -
are ready? Optional

System Test Execution

System Test Group


3
SYSTEM TEST PHASE (cont.)

System Test Coverage


All system features (feature testing)
Feature interactions
System performance
Capacity limits
Load and overload
Reliability
Recovery
Security
Installation
Conversion, and expansion.

4
SYSTEM TEST PHASE (cont.)

Deliverables to System Test


The following items must be delivered prior to system testing:
Release notes
Integration test report
Minimum hardware required
Test tools as identified in the system test plan.

5
SYSTEM TEST PHASE (cont.)

System Test Entrance Criteria


Test results/reports must be provided to System Test for
inspection

6
SYSTEM TEST PHASE (cont.)

Deliverables from System Test


Problem reports (PR’ s) if and when any problem is discovered
during testing which have not been reported before
At the conclusion of the system test phase, the distribution
media containing the successfully tested software will be
delivered to Acceptance
System test report and test results
System Test will also issue a report on the post-mortem of the
test effort for this test phase

7
SYSTEM TEST PHASE (cont.)

System Test Exit Criteria


System testing must successfully complete before it meets
the system test exit criteria (100% system test case
execution with the product quality requirements)
The system test report and test results must be made
available to the Acceptance Test group for inspection

Responsibility for the System Test Phase


The System Test Group is responsible for ensuring that this
test phase is carried out. In some instances, the System
Test Group may be augmented by a designated set of
designers

8
ACCEPTANCE TEST PHASE

Objective of the Acceptance Test Phase


Acceptance testing is focused upon determining the product’s
readiness to enter the marketplace. Acceptance test will simulate
typical customer scenarios in order to ensure that the product
operates acceptably in that environment. Testing in this phase is
not expected to uncover any significant technical problems.

9
ACCEPTANCE TEST RELATED ACTIVITIES
Participate in reviews of Commercial,
Product and Feature Specifications

Write Acceptance Test Plan & Test Cases

Acceptance Test Plan & Test Case Review

How many
Acceptance Test
related activities Acceptance Test Execution
are ready?

Acceptance Test Report / Verified


System Handover (to Field Trial)

Acceptance Test Groups


10
ACCEPTANCE TEST PHASE (cont.)

Acceptance Test Coverage


There are essentially four customer perspectives which provide
the direction for Product Verification:
End-user
Administrator
Distributor
Support (Product Support)

Test types:
Installation
Conversion
Upgrade
Modification
Network
Administration

11
ACCEPTANCE TEST PHASE (cont.)

Acceptance Test Coverage(cont.)


Compatibility
Support
Scenario
Documentation
On-line Help

12
ACCEPTANCE TEST PHASE (cont.)

Deliverables to Acceptance test


The following items must be delivered prior to acceptance
testing :
Distribution media containing software to be tested
Release notes providing all appropriate information on the
software release
Minimum hardware as required for the product under test
All test tools identified in the acceptance test plan
System test results/report

13
ACCEPTANCE TEST PHASE (cont.)

Acceptance Entrance Criteria


These items must be made available at the acceptance
meeting:
Product (hardware, firmware, software, and documentation)
quality must meet or exceed criteria
Workarounds and/or description must be available for all
open PR’ s
All system test cases must have been executed by the
System Test Group

14
ACCEPTANCE TEST PHASE (cont.)

Acceptance Entrance Criteria (cont.)


All system and designer test cases must be available for
audit by Acceptance
Test results for each test must be provided by development
for inspection. In the event of a “fail”, a PR number must also
be provided
Reviewed acceptance test plan must be available. All
acceptance test activity is provided in the test plan. The final
test plan and test cases are made available
Reviewed acceptance test cases must be available

15
ACCEPTANCE TEST PHASE (cont.)

Deliverables from Acceptance


Problem reports (PR’ s) if and when any problem is
discovered during testing which have not been reported
before
Acceptance test report and test results
Acceptance will also issue a report on the post-mortem of
the test effort for this test phase

16
ACCEPTANCE TEST PHASE (cont.)

Acceptance Exit Criteria


Acceptance will recommend a product that it tests if it has
quality and meets or exceeds customers’ requirements and
expectation based on the Product specifications

Responsibility for the Acceptance Test Phase


The Acceptance Group is responsible for ensuring that this
test phase is carried out

17

You might also like