Software TestingTest Design and Implementation

Agenda

• Test Design

• Test Implementation

• Test Design Sources

• Automated Testing

2

The Testing Process

3

• Planning and Design for testing is done in all phases of software development.

Determine the test methodology

Planning the tests

Designing the tests

Performing the tests

Test Methodology

Software Test Plan

Detailed DesignTest Case DB / File

Software Test Plan (STP)

• Scope of the Test S/W Package to be tested – name, version Document reference for the planned tests

• Testing Environment Testing Site Required H/W Config Participating Organizations Manpower Requirements Team Preparation – Training

• Test Details (for each test) Test ID Test Objective Reference to the Requirements Document (SRS) Test Class Test Level (Unit, Integration, System) Test Case Requirement Data to be Recorder

4

Software Test Plan (STP)

• Test Schedule Preparation Testing Error Correction Regression Tests

5

Test Design

• Output Software Test Procedure Test Case File

• Documented in “Software Test Description”

6

Software Test Description (STD)

• Scope of the Test S/W Package to be tested – name, version Document reference for the planned tests

• Testing Environment (for each test) Test ID Description of the H/W and OS Config. Instructions for S/W Loading (Setup)

• Test Process Instructions for input Data to be Recorded

• Test Cases (for each test case) Test Case ID Input Data and System Setting Expected Result

• Actions to be taken in case of failure7

Test Implementation

Test is carried out as mentioned in the STD

Identify and Fix the Errors

Regression Test (re-test) to check if the errors are removed

Check whether no new bugs were added when correcting

Repeat the correction-regression testing cycle until satisfactory results are achieved

Document the results in a report called Software Test Report (STR)

8

Software Test Report (STR)

• Test Details Software ID, Test Site Time of Start and End of Tests, Test Team Members, Other Participants, Time Taken for Test

• Test Environment Hardware Config. Prep and Training before the test

• Test Results Test ID Test Case Results (for each test case)

Test Case ID Tester ID Results Description if failed

9

Software Test Report (STR)

• Summary Tables Total Errors Their Distribution Types of Errors

• Special Cases Special Issues during the test implementation Problems identified during testing Proposal to change test environment Proposal to change test procedure and test case files

10

Note: Summary of tests is documented in Test Summary Report (TSR)

Test Im

ple

menta

tion P

hase

11

Test Design

STD

Testing

Is Quality Acceptable?

Correct Errors

Regression Test

End

STR

TSR

NOYES

STR

TSR

Test Design Components

12

TEST Test Case*

Data Inputs

Operating Conditions

Expected Results

Test ID Test Case ID

Input Condition Expected Actual

Example of Test Design

13

Let say the tax on a property is based on the following factorsS => Size of the apartmentN => Number of people living in the apartmentA, B, or C => Location Classification

If A = > Tax = (100*S)/(N+8)If B => Tax = (80*S)/(N+8)If C => Tax = (50*S) / (N+8)

Test IDTest Case

IDInput Condition Expected Actual

1 1.1 S=250Class APeople 2

$2500

1.2 S=180Class BPeople 4

$1200

1.3 S=98Class CPeople 6

$350

Test Case Sources

14

Sources

Real-Life Cases Synthetic Cases

Random Samples Simulated CasesCreated by Test DesignersBased on ExperienceCases that have high probability of failure

Sources for Test Cases

15

Real-life Case Synthetic Case

Effort Required to Prepare Test

Low Effort High Effort

Required Size of Test Case File

Relatively High Relatively Small

Efforts Required to Perform Test

High Effort Low Efforts

Effectiveness Relatively Low – Low coverageAbility to identify unexpected errors

Relatively HighGood CoverageUnexpected situations cannot be considered

Automated Testing

• Integration of computerized tools into the process of Software Development (or Testing specifically) Cost Savings Shorten Test Duration Detailed Performance of Tests Improvement of Test Accuracy Improvement in Result Reporting

• Automated Testing Activities Same as what we discussed earlier Planning, Design, Test Case Prep, Implementation, Log,

Report Prep, Regression Testing, Final Report

16

Automated Testing

• Types of Automated Testing Code Auditing

Check whether code complies with standards and Procedures Remember HTML Validation in Web-based Systems

Coverage Monitoring Line coverage achieved when designing test cases. Percentage of lines

covered and not-covered.

Functional Tests Record Black-Box Tests and perform them automatically Example: Junit for Unit Testing Java Modules

Load Tests Test the system under maximum load.

Test Management

17

Automated Testing

Advantages

• Accuracy and Completeness of Performance

• Accuracy of Result Log and Reports

• Comprehensive Information

• Few manpower

• Short duration of testing

• Perform complete regression testing

Disadvantages

• High Investment

• High development cost

• High manpower requirement for test prep

• Do not cover all areas of testing. Many needs to be done manually

18