Scribd
Upload
56 views20 pages

Software Testing Process

The document discusses system testing and implementation. It describes two types of system testing: pre-implementation testing to remove defects before production, and post-implementation testing as part of maintenance. Pre-implementation testing aims to identify and fix defects early, while post-implementation testing incurs additional costs to detect, report, and fix problems after deployment. The document also outlines an eleven-step process for V-model testing involving planning, requirements and design testing, program testing, acceptance testing, reporting, and evaluation.

Uploaded by

cdylie
Copyright
© Attribution Non-Commercial (BY-NC)
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
56 views20 pages

Software Testing Process

The document discusses system testing and implementation. It describes two types of system testing: pre-implementation testing to remove defects before production, and post-implementation testing as part of maintenance. Pre-implementation testing aims to identify and fix defects early, while post-implementation testing incurs additional costs to detect, report, and fix problems after deployment. The document also outlines an eleven-step process for V-model testing involving planning, requirements and design testing, program testing, acceptance testing, reporting, and evaluation.

Uploaded by

cdylie
Copyright
© Attribution Non-Commercial (BY-NC)
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/ 20

System Testing and Implementation

Testing Process
Tb. Maulana Kusuma
[email protected]

http://staffsite.gunadarma.ac.id/mkusuma

Gunadarma University undergraduate course - Tb. Maulana Kusuma 2006 – p. 1/20


Types of System Testing

• Pre-implementation testing.
To determine that the system functions as specified and that
defects in the system are removed prior to placing the
system into production (implementation).
• Post-implementation testing.
Part of system maintenance.

Gunadarma University undergraduate course - Tb. Maulana Kusuma 2006 – p. 2/20


Cost of Pre-Implementation Testing

• Building the defect into the system.


• Identifying existence of the defect.
• Correcting the defect.
• Testing to determine that the defect is removed.

Gunadarma University undergraduate course - Tb. Maulana Kusuma 2006 – p. 3/20


Cost of Post-Implementation Testing

• Specifying and coding the defect into the system.


• Detecting the problem within the application system.
• Reporting the problem to information services and/or the
user.
• Correcting the problems caused by the defect.
• Operating the system until the defect is corrected.
• Correcting the defect.
• Testing to determine that the defect no longer exists.
• Integrating the corrected program(s) into production.

Gunadarma University undergraduate course - Tb. Maulana Kusuma 2006 – p. 4/20


Cause of Defects

• Improperly interpreted requirements.


• Users specify wrong requirements.
• Requirements are incorrectly recorded.
• Design specifications incorrect.
• Program specifications incorrect.
• Program coding error.
• Program structural or instruction error.
• Data entry error.
• Testing error.
• Error correction mistake.
• Corrected condition causes another defect.

Gunadarma University undergraduate course - Tb. Maulana Kusuma 2006 – p. 5/20


V-Testing Concept

Gunadarma University undergraduate course - Tb. Maulana Kusuma 2006 – p. 6/20


Eleven-Step Testing

• Asses development plan and status.


• Develop the test plan.
• Test software requirements.
• Test software design.
• Program phase testing.
• Execute and record results.
• Acceptance test.
• Report test results.
• Test software installation.
• Test software changes.
• Evaluate test effectiveness.

Gunadarma University undergraduate course - Tb. Maulana Kusuma 2006 – p. 7/20


Eleven-Step V-Testing

Gunadarma University undergraduate course - Tb. Maulana Kusuma 2006 – p. 8/20


Step 1: Asses development plan and status

• Testing the validity of the software estimate.


• Testing the status of the software system.

Gunadarma University undergraduate course - Tb. Maulana Kusuma 2006 – p. 9/20


Step 2: Develop the test plan

• Form the test team.


• Understand the project risks.
• Build the test plan.
• Inspect the test plan.

Gunadarma University undergraduate course - Tb. Maulana Kusuma 2006 – p. 10/20


Step 3: Test software requirements

• Prepare a risk matrix.


• Perform a test factor analysis for the requirements phase
(methodology, correctness, ease-of-use, maintainable,
portable, coupling, performance, ease-of-operations,
reliability, authorization, file integrity, audit trail,
continuity-of-processing, service level, security).
• Conduct a requirements walk-through.

Gunadarma University undergraduate course - Tb. Maulana Kusuma 2006 – p. 11/20


Step 4: Test software design

• Score success factors.


• Analyze test factors.
• Conduct design review.
• Inspect design deliverables.

Gunadarma University undergraduate course - Tb. Maulana Kusuma 2006 – p. 12/20


Step 5: Program phase testing

• Desk debug the program.


• Perform program phase test factor analysis.
• Conduct a program peer review.

Gunadarma University undergraduate course - Tb. Maulana Kusuma 2006 – p. 13/20


Step 6: Execute and record results

• Build test data.


• Execute tests.
• Record test result.

Gunadarma University undergraduate course - Tb. Maulana Kusuma 2006 – p. 14/20


Step 7: Acceptance test

• Define the acceptance criteria.


• Develop an acceptance plan.
• Execute the acceptance plan (conduct acceptance tests
and reviews)
• Reach an acceptance decision.

Gunadarma University undergraduate course - Tb. Maulana Kusuma 2006 – p. 15/20


Step 8: Report test results

• Report software status.


• Report interim test results and individual component test
results.
• Report final test results.

Gunadarma University undergraduate course - Tb. Maulana Kusuma 2006 – p. 16/20


Step 9: Test software installation

• Test installation of new software.


• Test changed version (of software).
• Monitor production.
• Document problems.

Gunadarma University undergraduate course - Tb. Maulana Kusuma 2006 – p. 17/20


Step 10: Test software changes

• Develop/update the test plan.


• Develop/update the test data.
• Test the control change process.
• Conduct testing.
• Develop/update the training material.

Gunadarma University undergraduate course - Tb. Maulana Kusuma 2006 – p. 18/20


Step 11: Evaluate test effectiveness

• Establish assessment objectives.


• Identify what to measure.
• Assign measurement responsibility.
• Select evaluation approach.
• Identify needed facts.
• Collect evaluation data.
• Assess the effectiveness of testing.

Gunadarma University undergraduate course - Tb. Maulana Kusuma 2006 – p. 19/20


References
[1] William E. Perry, Effective Methods for Software Testing,
2nd ed., John Wiley & Sons, 2000.

Gunadarma University undergraduate course - Tb. Maulana Kusuma 2006 – p. 20/20

You might also like