DESIGNING

A
TEST PLAN

DESIGNING A TEST PLAN

Task 2
Once implementation is complete your website will need to be tested, to ensure it runs
smoothly and meets all of the functional requirements. As part of the design process you
have been asked to design a test plan for later use. Your test plan should include:

* Test name
* Test short description
* Test input
* Expected Result
* Actual Result
* Actions taken
* Minimum of 10 tests

You should add a notes section as an appendix, explaining why you chose each test and
input.

LEARNING OUTCOMES
2) Identify and describe issues when developing technical solutions.
By designing a test plan you are showing you understand any issues that could
occour when developing a dynamic website.
You should test all of the functionality of your website with emphasis on any
issues PHP and Mysql could cause.
NOTE: You could test security measures if you have added them but are not
necessary for this unit security will be covered next year.

TEST PLAN EXAMPLE

Test no /
name

Test
Description

Test input

Expected
Result

Authorise
d
login

Test login
system using
authorised user
details

Correct
username
and
password

User is
logged in
successfully

Unauthoris
ed Login

Test login
system using
unauthorised
user details

Incorrect
username or
password

User is not
logged in
and an error
message is
given

Search
for article

Search for an
article by date

Valid article
date

Actual
result

Actions

Articles
published on
the date will
be shown
NOTE: you only need to complete these four columns Actual result and action would
usually be completed once the website is complete and testing has taken place

NOTES
For each of your tests you need to write notes
Each notes should explain:
why you have included each test
Known issues you have tested for

For Example: Testing login

Dynamic websites offer great flexibility and allow users to register and view specific
pages. We need to test the login system to ensure that only those authorised can view
specific pages. Php brings flexibility but also can come with security vulnerabilities we
need to ensure these issues are not expoilted

TESTING FUNCTIONAL
REQUIREMENTS
Users can sign-up for a website account

Users can successfully login and view a members only section

Users can successfully logout
Users are able to view all of the current articles/news stories on the website
Users can search through articles/news stories on the website
Users can view news articles from specific dates
Users can view news articles from a specified date range
Journalists are able to login, upload, edit and delete their own articles
Journalists are able to add additional content to their articles (E.g. images,
videos, audio files etc.)
The editor should be able to login and edit/delete all journalists articles
Users can leave comments and feedback on articles

TESTING NON FUNCTIONAL

REQUIREMENTS
At the beginning of this module you should have made a list of Functional and
non functional requirements. You should test the non functional requirements of
your website aslo, to ensure it has the professional look required by the brief.
For Example
Do all links function correctly
Do all images load correctly
Do all pages load in a timely manner
Do all pages load with consistent CSS styling

READ THE GRADING CRITERA!

70+
Comprehensive and detailed test plan designed that covers all functional
requirements, with at least 20 test cases
Comprehensive notes explaining in detail your choice of tests and inputs
60 69
Test plan designed that covers most of the functional requirements, with at
least 15 test cases Your notes explain with a good attempt at detail, your
choice of tests and inputs

READ THE GRADING CRITERIA!

50-59%
Test plan designed that covers most of the functional requirements, with at
least 10 test cases
Your notes explain with a some attempt at detail, your choice of tests and
inputs
40-49%
Test plan designed that covers most of the functional requirements, with at
least 10 test cases
Your notes briefly explain your choice of tests and inputs