Beruflich Dokumente
Kultur Dokumente
com
Test Plan – TP101
2. Introduction
In order to provide a service that tells people over the web what time it is, Fog Creek
Software, Inc developed a Web site providing service “WhatTimeIsIt.com”. The initial
release of the Web site will be known as WhatTimeIsIt.com release 1.
The target audience will be for existing Fog Creek Software, Inc clients who would use
that service. Once the system is working successful, Fog Creek Software, Inc intends to
start an aggressive marketing campaign to attract clients for the online use of service
provided by WhatTimeIsIt.com.
Due to pressing business needs, Fog Creek Software’s traditional development and
testing processes have been customized to allow for faster and more frequent delivery
cycles. Specifically, testing will now consist of the following phases (listed
chronologically):
• Unit and integration level – adherence to coding standards and successful
communication between units
• Code Quality Assurance – acceptance into system level testing by successfully
repeating a small subset of tests performed in the code and integration level
• System level – compatibility, performance, usability, functionality etc.
• System Quality Assurance & Acceptance (acceptance into Production)
• Post Implementation
Each testing phase will be described within its own test plan (included as Appendixes
to the Master Test Plan). While the MTP (this document) may outline the overall
strategy and document the aspects of the resting are common to all of the phases.
3. Test Items
Testing will consist of several phase (see introduction), each phase may or may not
include testing of anyone or more of the following aspects of WhatTimeIsIt.com Web site
(listed alphabetically):
• Accessibility
• Audit
• Availability
• Coding standards
• Compatibility
• Content
• Functional
• Legal
• Marketing
• Navigation
• Performance
• Reliability
• Scalability
• Security
• Site recognition
• Usability
It is the intent that all of the individual test cases contained in each test plan will be
performed. However, if time does not permit, some of the low priority test cases may be
dropped.
6. Approach (Strategy)
The philosophy of the testing is risk-based testing, i.e. each test case will be prioritized as
High, Medium, or Low priority and then scheduled accordingly (Highest first).
Exceptions to this general rule might include instances where:
• A large number of low priority test cases can be executed using a small amount of
resources
• Scheduling conflicts arise e.g. the DBA is on vacation, thereby causing lower
priority tests (that do not need his assistance) to be scheduled while he is away
• A lower priority test is a pre-requisite of another higher priority test e.g. an
expensive and high priority usability test might necessitate many of the
inexpensive low priority navigational tests to have passes
• Due to the lack of comprehensive requirements, navigational and functional tests
may be scheduled first, so as to allow the testers the opportunity to gain familiarity
with the Web site (thereby also allowing them to developing pseudo requirements).
The testing will use a combination of a manual and automated testing, due to the limited
duration of the testing; only automated tools that are already familiar to the Fog Creek
Software staff or have a minimum learning curve will be used.
During period of test execution, the Web site’s source code will be frozen while being
tested. Except for critical fixes that are blocking the testing efforts, changes will not be
scheduled while a unit of code is being tested.
The entrance criteria’s for each phase of testing must be met before the next phase can
commence. Formal approval will be granted by the Project Manager.
The Project Director will retain the decision as to whether the total and/or criticality of
any or all detected incidents/defects warrant the delay (or rework) of the
WhatTimeIsIt.com release 1.0 Web site.
11.Environmental Needs
The following elements are required to support the overall testing efforts.
• Web application server
• SQL server
• Common PC machine with installed web browsers
It is preferred that there will be at least one (1) full time tester assigned to the project for
the system/integration and acceptance testing phases of the project. This will require
assignment of a person part time at the beginning of the project to participate in reviews
etc… and approximately two months into the project they would be assigned full time. If
a separate test person is not available the project manager/test manager will assume this
role.
In order to provide complete and proper testing the following areas need to be addressed
in terms of training.
• The developers will need to be trained on developing applications using HTML,
JavaScript and SQL Server communications process.
• The testers will need to be trained on basic operations of the common Web
browsers.
13.Responsibilities
TM PM Dev Test
Team Team
Acceptance test Documentation & Execution X X X
System/Integration test Documentation & Exec. X X X
Unit test Documentation & Execution X X X
System design Reviews X X X X
Detail design Reviews X X X X
Test procedures and rules X X X X
Screen & Report prototype reviews X X
14.Schedule
The following seeks to identify some of the more likely project risks and propose
possible contingencies:
• Web site becomes unavailable
• Web testing software is not available/does not work
• A large number of defects/incidents makes it functionally impossible to run all of
the test cases – as many test cases as possible will be executed.
• Not enough time to complete all test cases. If time cannot be extended, individual
test cases will be skipped, starting with the lowest priority.
16.Approvals
Terms and acronyms used in project documentation and during all development and test
phases.
• Splash Screen - A Shockwave animation that plays music and drives benefits of
using WhatTimeIsIt.com
• Log In Form - The Log in Form is used by current members to log into their
accounts in order to find out the current time
• Home Page – Provides some general info about WhatTimeIsIt.com and provides
account activities
• Display Time page – Provides a service
• SKIP THIS link - Clicking on SKIP THIS goes to Home Page
Test Case – TC101.1
Purpose – Test that user cannot log in with improper email address
Test Data – Email: testbad@domain.com
Steps:
1. Visit Log In Form on Login page
2. Enter email address (invalid)
3. See page again
4. Verify error message above the address box “The email address you
provided is not valid. Please double check it.” (the indicates problem)
Test message “Please enter your email address” still appears in black.