X Project Test Plan

X project
Test Plan
Version 1.0
© 2004, WWW.BUGHUNTRESS.COM
BUG HUNTRESS
Project: X project Version: 1.0
Document: Test Plan Date: 15/Sept/02
File: Test Plan_1.doc
Revision History
Date Version Description Author
05/Sep/02 1.0 Initial edition Alexandre Stelmakh
Example Page 2 of 15
BUG HUNTRESS
Table of Contents
1. Introduction 5
1.1 Purpose 5
1.2 Background 5
1.3 Scope 5
1.4 Project Identification 6
1.5 References 6
2. Requirements for Test 7

2.1 Functionality 7
2.1.1 Setup a user account 7
2.1.2 Remove user account 7
2.1.3 Connect and disconnect to ICQ service 7
2.1.4 Download contact list from server 7
2.1.5 Upload contact list to server 7
2.1.6 Add new contact to contact list 8
2.1.7 Delete contact from contact list 8
2.1.8 Create new message 8
2.1.9 Receive new message 8
2.1.10 Change connection status 8
2.1.11 Change current account 8
2.1.12 Change user status into idle 8
2.1.13 Message history 8
2.2 Usability 9
2.2.1 Sessions support 9
2.2.2 Fonts support 9
2.2.3 Automatic logon on application startup 9
2.2.4 Audible and flashing alerts 9
2.2.5 Graphical emoticons 9
2.2.6 Internet connection management 9
2.2.7 Display support 10
2.3 Design Constraints 10
2.3.1 Maximum message length 10
2.3.2 Supported Palm OS versions 10
2.3.3 Characters 10
2.4 Interfaces 10
2.4.1 User Interfaces 10
3. Test Strategy 11
3.1 Testing Types 11
3.1.1 Function and Usability Testing 11
3.1.2 User Interface Testing 11
3.2 Tools 11
BUG HUNTRESS
4. Resources 12
4.1 Roles 12
5. Project Milestones 13
6. Deliverables 14
6.1 Test Model 14
6.2 Test Logs 14
6.3 Bug Reports 14
Appendix A Project Tasks 15
BUG HUNTRESS
Test Plan
1. Introduction
1.1 Purpose
This Test Plan document for X project supports the following objectives:
• Identify existing project information and software components to be tested.
• List recommended Requirements for Test (high level).
• Recommend and describe testing strategies to be employed.
• Identify required resources and provide a test effort estimate.
• List the test project deliverable elements.
1.2 Background
The system developed is an instant messenger for Palm platform. The system should provide a capability
to use ICQ instant messaging service. So, the protocol used by this service must be supported by the
system.
The system developed is intended for Palm application market and positioned as standalone product.
1.3 Scope
This Test Plan describes the system tests that will be conducted within Build 1, Build 2, Build 3, Release
candidates and Release versions.
This Test Plan applies to testing all X project requirements defined in the Software Requirements
Specification [1].
BUG HUNTRESS
1.4 Project Identification

The table below identifies the documentation and availability used for developing the Test Plan:
Document Created or Received or Author or Notes

(and version / date) Available Reviewed Resource
Requirements Specification Yes No Yes No
Functional Specification Yes No Yes No
Use-Case Reports Yes No Yes No
Project Plan Yes No Yes No
Design Specifications Yes No Yes No
Prototype Yes No Yes No
User’s Manuals Yes No Yes No
Business Model or Flow Yes No Yes No
Data Model or Flow Yes No Yes No
Business Functions and Rules Yes No Yes No
Project or Business Risk Yes No Yes No

Assessment
1.5 References
The following table contains references to external documents.
Table 1 - Referenced documents

No. Document Description
[1] X project Software Requirements The SRS fully describes the external behavior of the
Specification, Version 1.0.3.3, application or subsystem identified. It also describes
Monday, 25/Aug/02 non-functional requirements, design constraints, and
other factors necessary to provide a complete and
comprehensive description of the software requirements.
[2] X project Software Development The purpose of Software Development Plan is to define
Plan, Version 1.0.5, 05/Sep/02 tasks of X project (hereinafter referred to as IM or the
project) to be developed. It focuses on the capabilities
sought after by stakeholders, the target users in
particular, and the reasons for this search.
[3]
BUG HUNTRESS
2. Requirements for Test

The listing below identifies those items − use cases, functional requirements, and non-functional
requirements − that have been identified as targets for testing. This list represents what is to be tested.
2.1 Functionality
2.1.1 Setup a user account
• Verify that the system provides the capability to setup user account for ICQ service.
• Verify that the system provides the capability to setup several user accounts.
• Verify that the system provides the capability to set option “Remember password” for each user
account individually.
2.1.2 Remove user account

• Verify that the system provides the capability to remove a user account from the system. To do that
the user should specify the user account to be removed. The system should ask the user to confirm the
removal. Then the user can cancel or confirm account removing.
2.1.3 Connect and disconnect to ICQ service

• Verify that the system provides the capability to connect to ICQ service.
• Verify that if an ICQ user account does not exist in the system it shall propose the user to set up a user
account.
• Verify that the system provides the capability to disconnect from ICQ service.
2.1.4 Download contact list from server

• Verify that the system provides the capability to download a contact list from the server. This
operation should be performed automatically during connection to ICQ service.
• Verify that the system provides the capability to disable automatic download of the contact list.
• Verify that the system provides the capability to download the contact list upon the user request.
2.1.5 Upload contact list to server

• Verify that the system provides the capability to upload a changed contact list to the server. This
operation should be performed automatically upon changing the contact list
• Verify that the system provides the capability to disable the contact list automatic upload.
• Verify that the system provides the capability to upload the contact list upon the user request.
BUG HUNTRESS
2.1.6 Add new contact to contact list

• Verify that the system provides the capability to add a contact to the contact list. To do this the user
should provide a UIN to be added.
The specified account exists, the user will be added to the contact list.
2.1.7 Delete contact from contact list

• Verify that the system provides the capability to delete a contact from the contact list. To do this the
user should specify a contact to be removed. The system should ask the user to confirm the removal.
Then the user can either cancel or confirm the contact removal.
2.1.8 Create new message

• Verify that the system provides the capability to create a new message. To create a new message the
user should select the message recipient from the contact list.
• Verify that the system provides the capability to type a new text message.
• Verify that the system provides the capability to send the created message to a specified recipient.
• Verify that the system provides the capability to cancel the message creation.
• Verify that the system provides this capability only for those users from the contact list.
2.1.9 Receive new message

• Verify that the system provides the capability to receive a message from ICQ service. This operation
should be performed automatically when a new message incomes. The system should indicate that the
new message has come from the sender whose name is highlighted in the user's contact list
2.1.10 Change connection status

• Verify that the system provides the capability to change the user connection status.
2.1.11 Change current account

• Verify that the system supports several user accounts for ICQ service.
• Verify that the system provides the capability to change an account for ICQ service without the
application shutdown. To do this the user should specify another account to log in.
2.1.12 Change user status into idle

• Verify that the system provides the capability to change the user status into idle automatically after the
user has been inactive for a specified time.
• Verify that the system provides the capability to specify that time interval.
2.1.13 Message history

• Verify that the system provides the capability to view message history.
• Verify that the system provides the capability to export message history to a memo (Memo pad
application).
BUG HUNTRESS
2.2 Usability
2.2.1 Sessions support
• Verify that the system provides the capability to open more than one message session at a time. Total
quantity of open sessions should only be limited to a maximum number of network connections and
available memory under Palm OS.
2.2.2 Fonts support

• Verify that the system provides the capability to select a custom font, font color and message
background color. These settings should be stored in user local profile and restored after the
application startup.
• Verify that the system displays the received messages with fonts, font colors and background color as
it is specified by the message sender (or at least with the closest style, taking into account font
limitations of Palm OS).
2.2.3 Automatic logon on application startup

• Verify that the system supports the option to connect automatically to ICQ account.
2.2.4 Audible and flashing alerts

• Verify that the system supports audible and flashing alerts for the following events:
o User from the contact list goes online.
o Incoming message.
o Error when sending a message.
• Verify that the system provides the capability to disable/enable alerts for each event type.
2.2.5 Graphical emoticons

• Verify that the system supports graphical emoticons displayed in incoming messages.
• Verify that the system provides the capability to insert graphical emoticons into outgoing messages.
2.2.6 Internet connection management

• Verify that the system provides the capability to choose the option “Automatically connect to Internet
on application startup”. If this option is enabled Internet connection should be initiated automatically
on the application startup. If there is no Internet connection on application startup the system should
display an error message.
• Verify that the system provides the capability to choose the option “Automatically disconnect from
Internet on application exit”. If this option is enabled Internet connection should be closed
automatically on the application exit.
• Verify that the system provides the capability to startup the application when Internet connection is
established. The system should provide the capability to enable/disable the feature mentioned.
BUG HUNTRESS
2.2.7 Display support

• Verify that the system supports color, grayscale and monochrome displays of Palm devices all in one.
• Verify that the system is self-adaptive to device capabilities. For Sony Clié devices 320x320
resolution and small fonts should be supported. For NR70 series s 320x480 resolution and small fonts
should be supported. For PalmOS5 high density API in 320x320 mode should be supported. For
standard Palm OS devices then the resolution should automatically adjust to 160x160.
2.3 Design Constraints

2.3.1 Maximum message length
• Verify that the system does not support messages longer than the maximum text limit allowed by
ICQ service.
2.3.2 Supported Palm OS versions

• Verify that the system runs on Palm OS 3.5 through Palm OS 5.0.
• Verify that the system runs on the latest version of Palm OS emulator equipped with Palm OS
ROMS from 3.5 through 4.1.
• Verify that the system also runs on Palm OS 5 Simulator.
2.3.3 Characters
• Verify that the application interacts correctly with Japanese Windows ICQ clients and Japanese
versions of Palm OS.
2.4 Interfaces
2.4.1 User Interfaces
• Verify that the system provides the user with an interface compatible with Palm OS User Interface
look and feel as in appendix A.
• Verify that all text input areas accept keyboard input, Japanese input, and graffiti shortcuts.
BUG HUNTRESS
3. Test Strategy
3.1 Testing Types
3.1.1 Function and Usability Testing
Test Objective: To ensure proper target-of-test functionality, including navigation, data entry,
processing, and retrieval.
Technique: Execute each use case, use-case flow, or function, using valid and invalid
data, to verify the following:
• The expected results occur when valid data are used.
• The appropriate error or alert messages are displayed when invalid data
are used.
Completion Criteria: • All planned tests have been executed.
• All identified defects have been fixed.
Special Considerations: Identify or describe those items or issues (internal or external) that impact the
implementation and execution of function test.
3.1.2 User Interface Testing

Test Objective: To verify the following:
• Navigation through the target-of-test properly reflects business-functions
and requirements, including window-to-window, field-to-field, and use
of access methods (tab keys, mouse movements, accelerator keys).
• Window objects and characteristics, such as menu size, position, state,
and focus conform to standards.
Technique: Create or modify tests for each window to verify proper navigation and object
states for each application window and object.
Completion Criteria: Each form is successfully verified and is consistent with benchmark version
or with acceptable standard.
Special Considerations: It is not every property of custom and third party objects that can be accessed.
3.2 Tools
The following tools are employed in this project:
Tool Vendor/In-house Version
Bug Tracking Mantis
Project Management MS project
BUG HUNTRESS
4. Resources
4.1 Roles
This table shows the staff required for the project.
Human Resources
Minimum Resources
Employee Recommended Specific Responsibilities/Job Description
(number of full-time roles allocated)
Test Developer Identifies, sets priorities for, and implements test cases.
Responsibilities:
• generates test plan
• evaluates effectiveness of test effort
Tester Executes tests.
Responsibilities:
• develops test case specifications
• develops test cases
• executes tests
• logs results
• monitors bug fixing
• requests for documentation to be changes
BUG HUNTRESS
5. Project Milestones
Test activities and milestones are very much dependent upon the development iterations. The Construction Phase is
split into 3 builds, release candidate and release version. Each build contains a full test cycle of test planning,
design, development, execution, and evaluation.
The following table shows Test Milestones. effort, start date, and end date.
Milestone Task Effort Start Date End Date
Build 1 123.7 07/Sep/2002 07/Sep/2002
Plan Test
Design Test
Execute Test
Evaluate Test
Build 2 88.7 16/Sep/2002 31/Sep/2002

Plan Test
Design Test
Execute Test
Evaluate Test
Build 3 57.2 01/Oct/2002 22/Oct/2002

Execute Test
Evaluate Test
Release candidate 57.2 22/Oct/2002 25/Oct/2002
Execute Test
Evaluate Test
Release version 57.2 25/Oct/2002 31/Oct/2002

Execute Test
Evaluate Test
BUG HUNTRESS
6. Deliverables
6.1 Test Model
Test Model defines all test cases, and references, test procedures and test scripts which are associated with
each test case.
6.2 Test Logs

Microsoft Word is used to record and report test results.
6.3 Bug Reports

Mantis bug tracker is used for logging and tracking individual malfunctions.
BUG HUNTRESS
Appendix A Project Tasks

Test-related tasks are given below:
• Test Planning
- identify requirements for testing
- assess risks
- develop test strategy
- identify test resources
- create schedule
- generate Test Plan
• Test Design
- prepare workload analysis
- identify and describe test cases
• Test Execution
- execute test procedures
- verify results
- investigate unexpected results
- log bugs
• Evaluate Test
- evaluate test-case coverage
- evaluate code coverage
- analyze defects
- determine whether Test Completion Criteria and Success Criteria have been achieved

X Project Test Plan

Hochgeladen von

Dokumentinformationen

Originalbeschreibung:

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

X Project Test Plan

Hochgeladen von

Copyright:

Verfügbare Formate

X project

2. Requirements for Test 7

Appendix A Project Tasks 15

1.4 Project Identification

Document Created or Received or Author or Notes

Requirements Specification  Yes  No  Yes  No

Functional Specification  Yes  No  Yes  No

Use-Case Reports  Yes  No  Yes  No

Project Plan  Yes  No  Yes  No

Design Specifications  Yes  No  Yes  No

Prototype  Yes  No  Yes  No

User’s Manuals  Yes  No  Yes  No

Business Model or Flow  Yes  No  Yes  No

Data Model or Flow  Yes  No  Yes  No

Business Functions and Rules  Yes  No  Yes  No

Project or Business Risk  Yes  No  Yes  No

Table 1 - Referenced documents

2. Requirements for Test

2.1.2 Remove user account

2.1.3 Connect and disconnect to ICQ service

2.1.4 Download contact list from server

2.1.5 Upload contact list to server

2.1.6 Add new contact to contact list

2.1.7 Delete contact from contact list

2.1.8 Create new message

2.1.9 Receive new message

2.1.10 Change connection status

2.1.11 Change current account

2.1.12 Change user status into idle

2.1.13 Message history

2.2.2 Fonts support

2.2.3 Automatic logon on application startup

2.2.4 Audible and flashing alerts

2.2.5 Graphical emoticons

2.2.6 Internet connection management

2.2.7 Display support

2.3 Design Constraints

2.3.2 Supported Palm OS versions

3.1.2 User Interface Testing

Build 2 88.7 16/Sep/2002 31/Sep/2002

Build 3 57.2 01/Oct/2002 22/Oct/2002

Release version 57.2 25/Oct/2002 31/Oct/2002

6.2 Test Logs

6.3 Bug Reports

Appendix A Project Tasks

Das könnte Ihnen auch gefallen

Requirements Specification Yes No Yes No

Functional Specification Yes No Yes No

Use-Case Reports Yes No Yes No

Project Plan Yes No Yes No

Design Specifications Yes No Yes No

Prototype Yes No Yes No

User’s Manuals Yes No Yes No

Business Model or Flow Yes No Yes No

Data Model or Flow Yes No Yes No

Business Functions and Rules Yes No Yes No

Project or Business Risk Yes No Yes No