Test Plan 1

BE05001

Revision History

Date Version Who Comments
08 January 2008 1.0 Nicholas Lavin Created initial document.
08 January 2008 1.1 Elizabeth Keyes Added test case 1.8.
09 January 2008 1.2 Elizabeth Keyes Change wording of test sample to test sample.

Introduction

Purpose

The purpose of the tests included in this plan is to verify that the software for our device is fully functional and meets the specifications we have set out for our software.

Feature Description

Our software will be used in order to control all aspects of our system. These test cases outline the software tests we will perform in order to verify that our device works when it is completed.

Test Strategy

Test Plans

Test 1.1: Cartridge Missing

Objective: The objective of this test is to verify that the device will properly detect a missing cartridge.
Type of Test: Unit Test
Testing Methodology: White Box
Procedure:

Preconditions:
The device is plugged in.
The device has been initialized.

Procedure::
The device's cartridge is removed.
The device is powered on.
Expected Results: The expected results are that the device displays an alert about the missing cartridge.
Final Results:
 This test has not been executed as of yet.
Test History: Refer to Result History

Test 1.2: Cartridge Empty

Objective: The objective of this test is to verify that the device can correctly detect that it has an empty cartridge.
Type of Test: Unit Test
Testing Methodology: White Box
Procedure:

Preconditions:
The device is plugged in.
The device is powered on.
The device has been initialized.

Procedure:
The device has an empty cartridge loaded.

Expected Results: The expected results are that the device displays an elert that the cartridge is low and should be replaced.
Final Results:
 This test has not been executed as of yet.
Test History: Refer to Result History

Test 1.3: Waste Missing

Objective: The objective of this test is to verify that the device can correctly detect that the waste receptacle is missing.
Type of Test: Unit Test
Testing Methodology: White Box
Procedure:

Preconditions:
The device is plugged in.
The device is powered off.
The device has been initialized.
The device's waste receptacle is removed.

Procedure:
The device is powered on.
Expected Results: The expected results are that the device displays an alert that the waste receptacle is missing.
Final Results:
 This test has not been executed as of yet.
Test History: Refer to Result History

Test 1.3: Waste Full

Objective: The objective of this test is to verify that the device can correctly detect that the waste receptacle is full.
Type of Test: Unit Test
Testing Methodology: White Box
Procedure:

Preconditions:
The device is plugged in.
The device is powered on.
The device has been initialized.
The device's waste receptacle is not full.
The waste receptacle is in place.

Procedure:
The device is operational while the wate receptacle is filled artifically.
Expected Results: The expected results are that the device displays an alert that the waste receptacle is full before overflowing.
Final Results:
 This test has not been executed as of yet.
Test History: Refer to Result History

Test 1.5: Sample Missing

Objective: The objective of this test is to verify that the device can correctly detect that the test sample is missing.
Type of Test: Unit Test
Testing Methodology: White Box
Procedure:

Preconditions:
The device is plugged in.
The device is powered on.
The device has been initialized.
The device is ready to load a test sample.

Procedure:
An attempt is made to use the device without inserting a test sample.
Expected Results: The expected results are that the device displays an alert that the test sample is missing.
Final Results:
 This test has not been executed as of yet.
Test History: Refer to Result History

Test 1.6: Barcode Fails to Scan

Objective: The objective of this test is to verify that the device can correctly handle the situation of a malfunctioning barcode reader.
Type of Test: Unit Test
Testing Methodology: White Box
Procedure:

Preconditions:
The device is plugged in.
The device is powered on.
The device has been initialized.
The device is ready to accept a barcode.

Procedure:
An attempt to read an incorrect barcode is initiated.
Expected Results: The expected results are that the device displays an alert that it could not read the barcode, and prompts for the user to enter patient information manually or attempt to scan the barcode again.
Final Results:
 This test has not been executed as of yet.
Test History: Refer to Result History

Test 1.7: Insufficient sample

Objective: The objective of this test is to verify that the device can correctly detect when there is not enough of the test sample to perform a test.
Type of Test: Unit Test
Testing Methodology: White Box
Procedure:

Preconditions:
The device is plugged in.
The device is powered on.
The device has been initialized.
The device is ready to accept a test sample.

Procedure:
A test sample with too little testing solution is put into the device.
The test is started.

Expected Results: The expected results are that the device displays an alert that it could not complete the test due to insufficient amount of the test sample.
Final Results:
 This test has not been executed as of yet.
Test History: Refer to Result History

Test 1.8: Cannot Connect to the Database

Objective: The objective of this test is to verify that the device will properly detect if it cannot send the test results to a medical database.
Type of Test: Unit Test
Testing Methodology: White Box
Procedure:

Preconditions:
The device is plugged in.
The device has been initialized.
The device has results for both tests.

Procedure::
The device is disconnected from a medical database.
Expected Results: The expected results are that the device displays an alert that it was unable to transfer results to database.
Final Results:
 This test has not been executed as of yet.
Test History: Refer to Result History