0% found this document useful (0 votes)
570 views3 pages

QA Strategy Test Plan

The document outlines a test plan for a smart transaction application including documentation to be used, the QA environment, testing process, risks, and high-level schedule. It describes the ability to create and void credit purchases and security features like login and password changes. Testing will involve functionality, validation, security, and regression testing using a manual approach.

Uploaded by

vishvinny
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 DOC, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
570 views3 pages

QA Strategy Test Plan

The document outlines a test plan for a smart transaction application including documentation to be used, the QA environment, testing process, risks, and high-level schedule. It describes the ability to create and void credit purchases and security features like login and password changes. Testing will involve functionality, validation, security, and regression testing using a manual approach.

Uploaded by

vishvinny
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 DOC, PDF, TXT or read online on Scribd

Smart Test Inc Transacion Application

QA STRATEGY Test Plan

1 Introduction
1.1 Document Scope

The purpose of this document is to specify how the delivery of the future application will be tested. It defines the following areas: Documentation to be used; QA environment; Testing process Potential ris s; !igh"level schedule. The document has been created based on the #cope documents provided by Pro$ect %anager.

1.2

Project Description
&.Ability to create credit purchase transaction. '.Ability to void it. (.#ecurity features.)login* change passwords+

2 Documentation
2.1 Specification Documentation
,e-uirement

for transaction application.

3 QA Environment
!P"Q. .entre &/./ for manual Testing and Tracebilty %atri0.

4 Testin Process
4.1 !"cle #ne

Test 1unctionality. 1ield 2alidation. Test #ecurity. 3ormal wal Through.

Page &

4.2

Su$se%uent !"cles

2erify fi0ed defects ,egression Test functionality around fi0ed defects. Testers will use their $udgement to decide how much regression testing is re-uired* based on the number and types of defects fi0ed in each version.

& 'is( )actors


34A

* Test Approac+
%anual Test Approach using Q. &/

, Test T"pe to $e performed


&. #ecurity Testing. '. 1unctionality Testing. (.1ield 2alidation45oundary condition Testing.

- Sc+edule
Delivery from Development: #ep* '/&( Delivery to the .ustomer: 6an* '/&7

Page '

You might also like