Test plan

test plan

1. Website http://project.com

Test Plan

Version 1.1




Шаблоны тест-планов:
1. Test Plan Template RUP (Rational Unified
Process)
2. Test Plan Template (стандарт IEEE 829)

2. Website http://project.com Version: 1.1
Test Plan Date: 25/01 /2016


Confidential <Company Name>, 2021 Page 2

Revision History

Date Version Description Author
20/01/2016 1.0 Creation DNK
25/01/2016 1.1 Edition DNK

3. Website http://project.com Version: 1.1
Test Plan Date: 25/01 /2016


Confidential <Company Name>, 2021 Page 3

Table of Contents
1. Introduction 4
1.1 Purpose 4
1.2 Background 4
1.3 Scope 4
2. Requirements for Testing Error! Bookmark not defined.
3. Test Strategy 4
3.1 Testing Types 6
3.1.1 Functional Testing 6
3.1.2 Cross Browser Testing 8
3.1.3 Regression Testing 8
3.1.4 User Interface Testing 8

4. Scheduled Work 9

5. Final Results 9
5.1 Conclusion 9

4. Website http://project.com Version: 1.1
Test Plan Date: 25/01 /2016


Confidential <Company Name>, 2021 Page 4

Test Plan
1. Introduction
1.1 Purpose

The purpose of the given Test Plan is the testing description of a website
PROJECT (full address - http://project.com). The document helps to gain (get,
obtain, receive) a better understanding about the scheduled work of a testing
project.
1.2 Background
PROJECT – is a website which gives the opportunity to get some interesting
information about ……; it also gives the opportunity to find out the information, to
look for data to search…, to achieve some knowledge about the product described.
1.3 Scope
The goal of testing the website is the thorough verification of all the features
in different browsers, their versions with the typical scripts of its usage. Some time
(about 20%) will be spent testing the negative scenarios which are also able to
uncover some bugs.
The final results of the testing process will be the following documents:
- the report about the testing results;
- documented bugs in the client’s bug tracking system.
The testing will be manual with the help of the ad-hoc method testing of a
Black Box.
2. Requirements for testing

PROJECT is to be a website which gives the opportunity to get some

5. Website http://project.com Version: 1.1
Test Plan Date: 25/01 /2016


Confidential <Company Name>, 2021 Page 5

interesting information about ……..to its users; it is also to give the opportunity to
find out the information, to achieve some knowledge about the product.
3. Test Strategy
As a result of the first testing cycle, where the functional tests take place,
there will be some corrections and additions made and put into the Test Plan. The
first cycle will give the definite understanding about the system stability and will
help to define the necessary test suite which will be executed shortly. Such method
will give the opportunity to get a detailed report about the product and will attract
the attention towards weak spots.
The client will be given all daily reports about the testing process, bugs found,
propositions about the improvements should be made. All the bugs found will be
added to the bug tracker for further corrections and fixes. While testing the
website, ad-hoc type of software testing will be implemented in view of strict
specification absence.
There are five stages of testing are planned:
the first stage – analysis, Test Plan creation, partial fulfillment of some
functional tests;
the second stage will be devoted to the detailed fulfillment of functional tests
uncovering and describing the bugs;
the third stage – Cross Browser testing with uncovering and description the
defects (bugs);
the forth stage is fixed bugs check and Regression testing fulfillment;
the fifth stage lies in User Interface testing with uncovering and description the
bugs.
Such kind of testing system allows fulfilling detailed testing and preventing,
fixing bugs on early stages.

6. Website http://project.com Version: 1.1
Test Plan Date: 25/01 /2016


Confidential <Company Name>, 2021 Page 6

OS:
Windows 7
MAC OS

Browsers:
Google Chrome 42.0
Opera 28.0
Firefox (latest)

Security and Load tests are not held in view of the lack of time.

3.1 Testing Types
1.3.1 Functional Testing
Aim target, purpose…:
Functional errors detection via functional tests fulfillment.

Process Description:
Registration/Logging in
Registration of a new user
New user’s logging in
Anonymous user
Password recovery
User’s profile edition
Feedback
Work under correct data filling

7. Website http://project.com Version: 1.1
Test Plan Date: 25/01 /2016


Confidential <Company Name>, 2021 Page 7

 Work under incorrect data filling
Search
News search, article search
Branch on tags
News mapping

Articles
Images display
Links workability
Backing off to the Main Page

Galleries
Photo paging
Correct zoom
Correct photos mapping

Banners
Correct banners mapping
Correct transition to the necessary pages


Captcha
 Renewal
Validation check

8. Website http://project.com Version: 1.1
Test Plan Date: 25/01 /2016


Confidential <Company Name>, 2021 Page 8

1.3.2 Cross Browser Testing

Target:
To check the correct work and user interface of the website in different browsers.
Browsers:
Google Chrome 42.0
Opera 28.0
Firefox (latest)
1.3.3 Regression Testing
Purpose:
To check the changes which were made in the website in order to make sure
that there are no bugs in the new version in the parts where testing had already
been made.
1.3.4 User Interface Testing
Goal:
To check the accordance of product’s design with the specification model set.
Process Description:
Registration form
Mail to a user
Website pages

9. Website http://project.com Version: 1.1
Test Plan Date: 25/01 /2016


Confidential <Company Name>, 2021 Page 9

4. Scheduled Work


Task Volume of work Starting date Expiry date
Test Plan Creation 12 hours 20.01.2016 …….2016
Test Execution
Analysis of testing
Summing-up



5. Final Results
5.1 Conclusion

The final result is a documented final result of testing process with the bug
descriptions and also with some recommendations and suggestions for further
improvement of the given product from the user’s point of view.