Scribd
Upload
35 views18 pages

Testing: Purpose in This Section Indicated The Purpose of The Accelerator .

This document contains information for testing a project, including the project name and number, customer details, managers assigned, and start and finish dates. It indicates test cases should provide descriptions of tests, preparation requirements, prerequisites, test procedures, and expected results, with any issues recorded. Test scenario documents should provide descriptions, prerequisites, test steps, screenshots, status comments, open issues, and assumptions.

Uploaded by

Arch tech
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as XLS, PDF, TXT or read online on Scribd
35 views18 pages

Testing: Purpose in This Section Indicated The Purpose of The Accelerator .

This document contains information for testing a project, including the project name and number, customer details, managers assigned, and start and finish dates. It indicates test cases should provide descriptions of tests, preparation requirements, prerequisites, test procedures, and expected results, with any issues recorded. Test scenario documents should provide descriptions, prerequisites, test steps, screenshots, status comments, open issues, and assumptions.

Uploaded by

Arch tech
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as XLS, PDF, TXT or read online on Scribd
You are on page 1/ 18

Testing

Purpose In this section indicated the purpose of the accelerator……..

Project Identification
Project Name Project Number Project Type

Customer Name Customer N Project Start. Finish

Project Sponsor Program Manager Project Manager (Customer)

Project Manager Service Partner(s) Project Manager (Service Partner)


Testing

ccelerator……..

pe

Project Start. Finish

Project Manager (Customer)

Project Manager (Service Partner)


Unit T

The test case should provide a description of the test, the details of all preparation required, t
Purpose
and any issues and/or errors will be recorded in the test case.

Project Identification

Project Name Project Number Project Type

Customer Name Customer Number

Project Sponsor Program Manager

Project Manager Service Partner(s)


Unit Test Results

of all preparation required, the prerequisites of the test, a detailed test procedure, and the expected test result. Test results

Project Start. Finish

Project Manager (Customer)

Project Manager (Service Partner)


ected test result. Test results
Test Result SAP

The test case should provide a description of the test, the details of all preparation required, the
Purpose prerequisites of the test, a detailed test procedure, and the expected test result. Test results and any
issues and/or errors will be recorded in the test case.

Version Control:
Version Number Update Date Author Summary of Change

Test Case:
Test Case ID:
Test Case Description:
Test Case Creator:
Estimated Duration:
Priority:
Function Specification
Technical Specification

Prerequisites:
Prerequisite Description Comments/Notes

N/A

Test Scenarios:
Scenario ID Scenario Description Tester Test Date Test Scenario
status (Pass/Fail)

Scenario1

Scenario2

Issue Log:
Step # Date Description of Issue Priority Status
Code Inspector Result

Test, Review and Approvals:


Assignments Signature Date
Tester
Reviewer (Peer)
Reviewer (TL)
Reviewer (QA)

Open Issue(s):

Assumption(s):
Purpose

Scenario Details:
Test Case ID:
Scenario ID:
Scenario Description:
Estimated Duration:
Priority:

Prerequisites:
Prerequisite Description

Test Step:
Step Step Detail

2
3

Screen Capture:

Status:
Status: Comments (Pass / Fail - with
defect number)

Open Issue(s):

Assumption(s):
Test Scenario Result SAP

This scenario document should provide description of the scenario


case, the prerequisites of the test, a detailed test procedure, and the
expected test result. It should also provide the refence to the test case
it belongs to.

Comments/Notes

Input Data
Date
Test Scenario Result

This scenario document should provide description of the scenario case


Purpose prerequisites of the test, a detailed test procedure, and the expected tes
should also provide the refence to the test case it belongs to.

Scenario Details:
Test Case ID:
Scenario ID:
Scenario Description:
Estimated Duration:
Priority:

Prerequisites:
Prerequisite Description Comments/Notes

Test Step:
Step Step Detail Input Data

2
3

Screen Capture:

Status:
Status: Comments Date
(Pass / Fail
- with
defect
number)

Open Issue(s):

Assumption(s):
st Scenario Result SAP

ent should provide description of the scenario case, the


st, a detailed test procedure, and the expected test result. It
he refence to the test case it belongs to.

Expected Result A
c
t
u
a
l
R
e
s
u
l
t

You might also like