搜档网
当前位置:搜档网 › test summary report

test summary report

test summary report
test summary report

Test Summary Report

for

Project

DATE

1.0 Identification

OUR PROJECT .

2.0 Description of Test Environment

A single database test environment was used to test the Our project. The database was configured similar

to the clients own set up. The database was set on a HPUX server running 10.10 operating system. The version of Oracle was 7.2.2.3.0.

The configuration of the client workstations was 100MHz Pentium and 32 MB of RAM running the NT 4.0 and windows 95 operating system.

The Our process was set up on NT 4.0 desktop operating system with 100MHz processor and 32 MB of RAM.

3.0 Test Strategy

? A test summary was developed for the Cross functional team to review the test strategy.

? A test plan was developed to specifically identify and describe how the tests cases were to be executed. ? The automation tool SQA Robot version 6.0 was used for boundary testing.

? The testing mainly focused on the Our Projects process it self not the client, however QA did note and log numerous client issues.

? Install testing was done from the diskette to the NT machine.

4.0 Summary

The testing of the O ur Project took 25 days. There were three separate builds done after the code was first sent to QA. The first build was due to issue 4483, the fact that when the process encountered a record too big for the file it aborted the process. It was decided by product development to change the value to 9999999999 in the detail section if it goes over 10 digits. If the total exceeds 10 digits, then the total figure would be filled with 9999999999 and Arbor will reject the file.

The second build resulted when the imported the files into a system and the files did not work. The reason was because the information communicated to our company from the other company was not complete. The incorrect information was;

1. The name of the Our file was incorrect.

2. The total count in the last trailer record must include all lines in the file.

3. The detail records "check column" needed to be a "payment total" not the "check total".

The third build resulted because the name of the imported file was still incorrect. The original document required the Our file to have the extension .dat, however Arbor could not process the file with this extension.

It was decided after the third round of testing that QA would do installation testing. The documented installation test was delayed due to the fact that development did not have an installation kit made. QA had to reject the first kit made because a critical SQL script was missing and another SQL script

was written incorrectly. QA finished the installation testing and forward the disk and files to product management and client services.

In total 15 issue were uncovered in the three testing cycles, 20% were with the process and 80% were with the client. Since the customer already has the client portion installed, it was decided that all client issues would be postponed until the next client release.

QA was asked to provide the documentation team with instructions on how to set the client up. This was done in the document OUR PROJECT clientsetup.doc, which resides on the teams folder on NT SERVER. QA also provided the team a list of release notes in the document QANotesforReleaseNotes OUR PROJECT.doc, which also resides on the team folder on NT Server. QA also made changes to the NT installation guide based on there findings from the install test.

5.0 Metrics

Test Timeframe M/D/YY to M/DD/YY

Total Days22 days, 75.5 hours of testing

Number of builds3

Resources 1 full time, 3 part time

Total tests267

Total tests completed602

Total tests automated 4

Total Hours154.5 - includes planning, troubleshooting

problems and actual test execution.

Test Preparation Time Total 79 Hours

Test Execution Time Total 75.5 Hours

Build 1 27

Build 2 28.5

Build 3 15

Build 4 1

Install Test1 2

Install Test2 2

Defect Summary

Total found 15 defects found from QA testing

Total canceled/closed 1 6 %

6.0 Risk Assessment

With possible risk assessments of low, medium and high the risk assessment for OUR PROJECT for is High. Below please find a detailed summary of risk factors.

Risk Factor Recommendations

7.0 Known Defect List

ISSUE Type Priority Description Impact

相关主题