1. Introduction
This Test Plan Version 1.1
provides the strategy for testing the project “Cluster Management Systems”.
This section of the Test Plan document describes the following.
·
Purpose
·
Objectives
a. Document Purpose
This Test Plan
reviews:
i.
Existing
project information,
ii.
Business
Requirements and critical transactions to be tested,
iii.
Testing
types and strategies to be implemented and
iv.
A
proposed testing schedule
b. Objectives
This
document provides the platform for testing the project “Cluster Management
System”. The objective of testing is to see if
the project meets the “Software Requirement Specifications version 2.0”. This document will provide - (1) the guidelines for
the testing team to test the functionalities embedded in the project and (2) help
for evaluating the Software Quality of the project.
2. Project Scope
This section of the Test Plan document describes the (1) Scope
of the project “Cluster Management System” and (2) Out of Scope of the project “Cluster
Management System”.
a. Scope of the Project
“Cluster Mangement System” will be tested for its functionality on
a cluster of 3 computers. Each computer on the cluster is a Pentium III (548
MHz) with Linux operating system. Testing include – (1) Unit testing, (2) Integration testing, (3)
System testing and (4) Customer Acceptance Testing (CAT). Each test is
scheduled to take one week with the Customer Acceptance test on 11-11-2008.
The
testing includes testing for several functions like
·
Login feature
·
Adding or deleting of an user
·
Reboot a node
·
Updating a user profile
·
Adding or Deleting a node
1. Out of Scope of the Project
Performance of the project “Cluster Management
System” for a cluster of large number of computers is out of scope of this
project at this point of time.
3. Project Resources
Table 1 describes the
Roles, Responsibilities and Resource Name for the testing of the Project “Cluster
Management System”.
Role
|
Responsibilities
|
Resource Name(s)
|
Testers |
ü
Plan
testing activities
ü
Execute
Test Cases
ü
Find,
report and track defects
ü
Measure
test effort
ü
Analyze
results
|
Prasad
and chaitanya
|
Developers
|
ü
Deliver
complete builds of the application
ü
Provide
Testers with feedback regarding changes, new functionality
ü
Provide
expertise and knowledge of the application-under-test
ü
Eliminate
agreed upon defects
|
Nilesh
|
Business
Analysts
|
ü
Interview
Users
ü
Create
Business Requirements
ü
Create
Test Scenarios, Test Cases
|
Chaitanya
and Prasad
|
Users
|
ü
Describe
and review Business Requirements
ü
Describe
and review user profiles
ü
Perform
Customer Acceptance Testing (CAT)
|
Nilesh,Prasad
and Chaitanya
|
Desktop
Administrators
|
ü
Installation
of software
ü
Troubleshooting
of hardware/software
ü
Information
regarding standard desktop
|
Nilesh
Nilesh
Nilesh
|
Table 1 - Project Roles and Responsibilities
4. Test Strategies/Techniques
This section of the
document describes – (1) Test design and (2) Test Data for the project “
Cluster Management System”.
a. Test Design
Considering the scope of the project and the time
limitations, we will be performing following tests.
a)
Unit Test –
This test verifies the program logic and is
based on the knowledge of the program structure.
b)
Integration Test –
This test verifies the entire system’s
functionality according to the design specification.
c)
Business Requirements –
This test verifies whether specific requirements
of the customer are met.
d)
Acceptance Testing –
This
test verifies whether the system needs to meet the initial objectives and customer’s
expectations.
For performing the above mentioned tests, we will create test cases as
shown in table 2.
|
Table
2 - Use cases and Test Cases
Table 3 describes the description of each test case
mentioned in table 2 and the results expected from a corresponding test case.
Test Case
|
Use Case ID
|
Description
|
Expected
Result
|
TC-1
|
UC-1
|
User enters a valid
customer ID and password
|
User is granted the access to
the system
|
TC-2
|
UC-2
|
User edits information he
wants to update in view user profile section
|
A message is displayed whether
to confirm update or cancel and return back to view user profile page.
|
TC-3
|
UC-3
|
Admin clicks the
reboot button after accessing the node lists.
|
A message will appear that
rebooting operation is taking place. Once the machine is powered on, power
button will become green
|
TC-4
|
UC-4
|
Admin clicks
add/delete user menu button and fills the form ‘Add/delete a single user’
|
Message will appears
that
User was successfully
created/deleted.
|
TC-5
|
UC-5
|
Admin clicks on
nodes button and selects add/delete node option
|
Confirmation screen is
displayed verifying that selected nodes are added/deleted
|
TC-6
|
UC-6
|
Admin clicks the
nodes button , Once the nodes are listed, click Red power button
|
“Powering On” message will be
displayed until the machine is completely powered on Once the machine is
powered on, the power button will become green.
|
TC-7
|
UC-7
|
Admin clicks the
Accounts button and clicks list users menu item
|
.A screen will be displayed listing
all users.
|
Table
3 – Description and the Expected Results of each Test Case
b. Database
A
Head node maintains Database that
contains the login names and passwords of all the users and administrator.
5. Project Tasks/Schedule
Table 4
describes the schedule for the Test Plan of the project “Cluster Management
System
Task
|
Artifacts
|
Projected Completion
|
Test Plan Completed
|
Test
Plan Version 1.0
|
10-20-2008
|
Test Environment Prepared
|
Hardware
and software
|
10-13-2008
|
Test Cases Recorded and
Executed
|
Cluster,
Test Plan Document version 1.0, Test Results Document
|
10-17-2008
|
Defects submitted and tracked
|
Unit
Test Results Document
|
11-05-2008
|
Integration test
|
Test
Plan Document Version 1.0
|
11-08-2008
|
Customer Acceptance Test
|
Test
Plan Document Version 1.0
|
11-11-2008
|
Table
4 - Project Schedule
6. Defect Responsibility/Resolution
Possible
defects identified through manual testing will be discussed with development
team members to verify that the observed behavior constitutes a defect. Defects
found will be tried to be resolved. If not possible, they will be delivered
with the deliverables as “Known Bugs”. Defect register will be maintained to keep a
track of all the defects found in the software.
7. Exit Criteria
Testing can proceed to the next stage of the process when a
sufficient proportion of the current stage has been completed All exit criteria
should be satisfied by the end of the project.
8) Goals and Deliverables
Goals and deliverables of the test
plan of the “Cluster Management System” are as follows –
a) Goals:
ü To accomplish all
tasks described in this test plan.
ü To install a
measurable, improvable, repeatable, and manageable test process.
ü To verify the functionality
and content of the current version of the application.
ü To reduce the
frequency of error associated with manual testing.
ü
To
find and successfully track 100% of defects present along the user path defined
in this plan.
b)
Deliverables:
ü Test Planning Stage
ü Test Execution and Defect Tracking Stage
ü Evaluation and Improvement – this include
§ Test Cycle Evaluation
§ Project Summary /
Evaluation
