Acronym Definition
SYTP System Test Plan
SYTP Syndicat Yvelinois Travaux Publics
SYTP System Training Program
SYTP Scottish Youth Theatre Program
SYTP See You Tomorrow Plan
SYTP Shankill Young Tartan Psycho
SYTP South Yorkshire Times Partners
SYTP Standard Young Tableaux Program
SYTP Sweet Young Thing Person
SYTP South Yorkshire Transport PTE
SYTP South Yorkshire Transport Passenger
SYTP Standard Yahoo Translating Proxy
SYTP Standard Yahoo Trip Planner
SYTP Standard Yayasan Tafean Pah
SYTP Standard Yearly Training Plan
SYTP Standard Yearly Training Program
SYTP Standard Yeni Turkiye Partisi (Turkish: New Turkey Party)
SYTP Standard Yeniden Turkiye Partisi
SYTP Standard Yield to Put (securities-bonds)
SYTP Standard Yokosuka Teen Programs
SYTP Standard Yorkshire Training Partnership (UK)
SYTP Standard You the People
SYTP Standard You're the Psycho
SYTP Standard Young Tourism Professionals
SYTP Standard Your Town Press (Salem, Oregon)
SYTP Standard Youth Training Program
SYTP Standard Youth Transition Program
SYTP Standard Youth Travel Partners
SYTP Standard Youth Travel Polska
SYTP Standard Youth Travel Program
SYTP Standard Youth Tutoring Program
SYTP Screw You Teacher's Pet
SYTP See You/Ya Travel Pass
SYTP Sustained yield timber production
A test plan is a systematic approach to testing a system such as a machine or
software. The plan typically contains a detailed understanding of what the
eventual workflow will be.
Test plans in software development
In software testing, a test plan gives detailed testing information regarding an
upcoming testing effort, including
* Scope of testing
* Schedule
* Test Deliverables
* Release Criteria
* Risks and Contingencies
Test plan template, based on IEEE 829 format
1. Test Plan Identifier (TPI).
2. References
3. Introduction
4. Test Items
5. Software Risk Issues
6. Features to be Tested
7. Features not to be Tested
8. Approach
9. Item Pass/Fail Criteria
10. Entry & Exit Criteria
11. Suspension Criteria and Resumption Requirements
12. Test Deliverables
13. Remaining Test Tasks
14. Environmental Needs
15. Staffing and Training Needs
16. Responsibilities
17. Planning Risks and Contingencies
18. Approvals
Test plan identifier
For example: "Master plan for 3A USB Host Mass Storage Driver TP_3A1.0"
Some type of unique company generated number to identify this test plan, its
level and the level of software that it is related to. Preferably the test plan
level will be the same as the related software level. The number may also
identify whether the test plan is a Master plan, a Level plan, an integration
plan or whichever plan level it represents. This is to assist in coordinating
software and testware versions within configuration management.
Keep in mind that test plans are like other software documentation, they are
dynamic in nature and must be kept up to date. Therefore, they will have
revision numbers.
You may want to include author and contact information including the revision
history information as part of either the identifier section of as part of the
introduction.
References
List all documents that support this test plan.
Documents that are referenced include:
* Project Plan
* System Requirements specifications.
* High Level design document.
* Detail design document.
* Development and Test process standards.
* Methodology
* Low level design
Introduction
State the purpose of the Plan, possibly identifying the level of the plan
(master etc.). This is essentially the executive summary part of the plan.
You may want to include any references to other plans, documents or items that
contain information relevant to this project/process.
Identify the objective of the plan or scope of the plan in relation to the
Software Project plan that it relates to. Other items may include, resource and
budget constraints, scope of the testing effort, how testing relates to other
evaluation activities (Analysis & Reviews), and possible the process to be used
for change control and communication and coordination of key activities.
As this is the "Executive Summary" keep information brief and to the point.
Test items (functions)
These are things you intend to test within the scope of this test plan.
Essentially, something you will test, a list of what is to be tested. This can
be developed from the software application inventories as well as other sources
of documentation and information.
This can be controlled on a local Configuration Management (CM) process if you
have one. This information includes version numbers, configuration requirements
where needed, (especially if multiple versions of the product are supported). It
may also include key delivery schedule issues for critical elements.
This section can be oriented to the level of the test plan. For higher levels it
may be by application or functional area, for lower levels it may be by program,
unit, module or build.
Software risk issues
Identify what software is to be tested and what the critical areas are, such as:
1. Delivery of a third party product.
2. New version of interfacing software.
3. Ability to use and understand a new package/tool, etc.
4. Extremely complex functions.
5. Modifications to components with a past history of failure.
6. Poorly documented modules or change requests.
There are some inherent software risks such as complexity; these need to be
identified.
1. Safety.
2. Multiple interfaces.
3. Impacts on Client.
4. Government regulations and rules.
Another key area of risk is a misunderstanding of the original requirements.
This can occur at the management, user and developer levels. Be aware of vague
or unclear requirements and requirements that cannot be tested.
The past history of defects (bugs) discovered during Unit testing will help
identify potential areas within the software that are risky. If the unit testing
discovered a large number of defects or a tendency towards defects in a
particular area of the software, this is an indication of potential future
problems. It is the nature of defects to cluster and clump together. If it was
defect ridden earlier, it will most likely continue to be defect prone.
One good approach to define where the risks are is to have several brainstorming
sessions.
* Start with ideas, such as, what worries me about this project/application.
Features to be tested
This is a listing of what is to be tested from the user's viewpoint of what the
system does. This is not a technical description of the software, but a USERS
view of the functions.
Set the level of risk for each feature. Use a simple rating scale such as High,
Medium and Low(H, M, L). These types of levels are understandable to a User. You
should be prepared to discuss why a particular level was chosen.
Sections 4 and 6 are very similar, and the only true difference is the point of
view. Section 4 is a technical type description including version numbers and
other technical information and Section 6 is from the User’s viewpoint. Users do
not understand technical software terminology; they understand functions and
processes as they relate to their jobs.
Features not to be tested
This is a listing of what is 'not' to be tested from both the user's viewpoint
of what the system does and a configuration management/version control view.
This is not a technical description of the software, but a user's view of the
functions.
Identify why the feature is not to be tested, there can be any number of
reasons.
* Not to be included in this release of the Software.
* Low risk, has been used before and was considered stable.
* Will be released but not tested or documented as a functional part of the
release of this version of the software.
Sections 6 and 7 are directly related to Sections 5 and 17. What will and will
not be tested are directly affected by the levels of acceptable risk within the
project, and what does not get tested affects the level of risk of the project.
Approach (strategy)
This is your overall test strategy for this test plan; it should be appropriate
to the level of the plan (master, acceptance, etc.) and should be in agreement
with all higher and lower levels of plans. Overall rules and processes should be
identified.
* Are any special tools to be used and what are they?
* Will the tool require special training?
* What metrics will be collected?
* Which level is each metric to be collected at?
* How is Configuration Management to be handled?
* How many different configurations will be tested?
* Hardware
* Software
* Combinations of HW, SW and other vendor packages
* What levels of regression testing will be done and how much at each test
level?
* Will regression testing be based on severity of defects detected?
* How will elements in the requirements and design that do not make sense or are
untestable be processed?
If this is a master test plan the overall project testing approach and coverage
requirements must also be identified.
Specify if there are special requirements for the testing.
* Only the full component will be tested.
* A specified segment of grouping of features/components must be tested
together.
Other information that may be useful in setting the approach are:
* MTBF, Mean Time Between Failures - if this is a valid measurement for the test
involved and if the data is available.
* SRE, Software Reliability Engineering - if this methodology is in use and if
the information is available.
How will meetings and other organizational processes be handled?
Item pass/fail criteria
Show stopper issues. Specify the criteria to be used to determine whether each
test item has passed or failed. Show Stopper severity requires definition within
each testing context.
Entry & exit criteria
Specify the criteria to be used to start testing and how you know when to stop
the testing process.
Suspension criteria & resumption requirements
Suspension criteria specify the criteria to be used to suspend all or a portion
of the testing activities while resumption criteria specify when testing can
resume after it has been suspended.
For example, System Integration Testing in Integration environment can be
suspended in the following circumstances:
* Unavailability of external dependent systems during execution.
* When a tester submits a "Critical" or "Major" defect, the Testing Team will
call a break in testing while an impact assessment is done
* When the Sanity Tests fail.
System Integration Testing in the Integration environment may be resumed under
the following circumstances:
* When the "Critical" or "Major" defect is resolved
* When the defect from the Sanity Test is resolved and available for re-testing
* When a fix is successfully implemented and the Testing Team is notified to
continue testing
Test deliverables
List documents, reports, charts, that will be presented to stakeholders on a
regular basis during testing and when testing has been completed.
Remaining test tasks
If this is a multi-phase process or if the application is to be released in
increments there may be parts of the application that this plan does not
address. These areas need to be identified to avoid any confusion should defects
be reported back on those future functions. This will also allow the users and
testers to avoid incomplete functions and prevent waste of resources chasing
non-defects.
If the project is being developed as a multi-party process, this plan may only
cover a portion of the total functions/features. This status needs to be
identified so that those other areas have plans developed for them and to avoid
wasting resources tracking defects that do not relate to this plan.
When a third party is developing the software, this section may contain
descriptions of those test tasks belonging to both the internal groups and the
external groups.
Environmental needs
Are there any special requirements for this test plan, such as:
* Special hardware such as simulators, static generators etc.
* How will test data be provided. Are there special collection requirements or
specific ranges of data that must be provided?
* How much testing will be done on each component of a multi-part feature?
* Special power requirements.
* Specific versions of other supporting software.
* Restricted use of the system during testing.
Staffing and training needs
Training on the application/system.
Training for any test tools to be used.
The Test Items and Responsibilities sections affect this section. What is to be
tested and who is responsible for the testing and training.
Responsibilities
Who is in charge?
This issue includes all areas of the plan. Here are some examples:
* Setting risks.
* Selecting features to be tested and not tested.
* Setting overall strategy for this level of plan.
* Ensuring all required elements are in place for testing.
* Providing for resolution of scheduling conflicts, especially, if testing is
done on the production system.
* Who provides the required training?
* Who makes the critical go/no go decisions for items not covered in the test
plans?
Planning risks and contingencies
What are the overall risks to the project with an emphasis on the testing
process?
* Lack of personnel resources when testing is to begin.
* Lack of availability of required hardware, software, data or tools.
* Late delivery of the software, hardware or tools.
* Delays in training on the application and/or tools.
* Changes to the original requirements or designs.
* Complexities involved in testing the applications
Specify what will be done for various events, for example:
Requirements definition will be complete by January 1, 20XX, and, if the
requirements change after that date, the following actions will be taken:
* The test schedule and development schedule will move out an appropriate number
of days. This rarely occurs, as most projects tend to have fixed delivery dates.
* The number of tests performed will be reduced.
* The number of acceptable defects will be increased.
o These two items could lower the overall quality of the delivered product.
* Resources will be added to the test team.
* The test team will work overtime (this could affect team morale).
* The scope of the plan may be changed.
* There may be some optimization of resources. This should be avoided, if
possible, for obvious reasons.
Management is usually reluctant to accept scenarios such as the one above even
though they have seen it happen in the past.
The important thing to remember is that, if you do nothing at all, the usual
result is that testing is cut back or omitted completely, neither of which
should be an acceptable option.
Approvals
Who can approve the process as complete and allow the project to proceed to the
next level (depending on the level of the plan)?
At the master test plan level, this may be all involved parties.
When determining the approval process, keep in mind who the audience is:
* The audience for a unit test level plan is different from that of an
integration, system or master level plan.
* The levels and type of knowledge at the various levels will be different as
well.
* Programmers are very technical but may not have a clear understanding of the
overall business process driving the project.
* Users may have varying levels of business acumen and very little technical
skills.
* Always be wary of users who claim high levels of technical skills and
programmers that claim to fully understand the business process. These types of
individuals can cause more harm than good if they do not have the skills they
believe they possess.
Glossary
Used to define terms and acronyms used in the document, and testing in general,
to eliminate confusion and promote consistent communications.
Regional differences
There are often localized differences in the use of this term. In some
locations, test plan can mean all of the tests that need to be run. Purists
would suggest that a collection of tests or test cases is a Test suite.
Some locations would consider what is described above as a test strategy. This
usage is generally localized to the Indian market.
Some state that a test strategy creation precedes the test plan creation (ISTQB
among others) , others suggest that it follows the test plan creation.
Criticism of the overuse of test plans
Cem Kaner, co-author of Testing Computer Software (ISBN 0-471-35846-0), has
suggested that test plans are written for two very different purposes. Sometimes
the test plan is a product; sometimes it's a tool. It's too easy, but also too
expensive, to confuse these goals. In other words, a test plan is like a power
tool. You should not utilize them if you don't know what you're doing with them.
You are wasting both time and money.
Test plans in hardware development
A test plan documents the strategy that will be used to verify and ensure that a
hardware product or system meets its design specifications and other
requirements. A test plan is usually prepared by or with significant input from
Test Engineers.
Depending on the product and the responsibility of the organization to which the
test plan applies, a test plan may include one or more of the following:
* Design Verification or Compliance test - to be performed during the
development or approval stages of the product, typically on a small sample of
units.
* Manufacturing or Production test - to be performed during preparation or
assembly of the product in an ongoing manner for purposes of performance
verification and quality control.
* Acceptance or Commissioning test - to be performed at the time of delivery or
installation of the product.
* Service and Repair test - to be performed as required over the service life of
the product.
A complex system may have a high level test plan to address the overall
requirements and supporting test plans to address the design details of
subsystems and components.
Test plan document formats can be as varied as the products and organizations to
which they apply, but there are three major elements of a test strategy that
should be described in the test plan: Test Coverage, Test Methods, and Test
Responsibilities.
Test coverage in the test plan states what requirements will be verified during
what stages of the product life. Test Coverage is derived from design
specifications and other requirements, such as safety standards or regulatory
codes, where each requirement or specification of the design ideally will have
one or more corresponding means of verification. Test coverage for different
product life stages may overlap, but will not necessarily be exactly the same
for all stages. For example, some requirements may be verified during Design
Verification test, but not repeated during Acceptance test. Test coverage also
feeds back into the design process, since the product may have to be designed to
allow test access (see Design For Test).
Test methods in the test plan state how test coverage will be implemented. Test
methods may be determined by standards, regulatory agencies, or contractual
agreement, or may have to be created new. Test methods also specify test
equipment to be used in the performance of the tests and establish pass/fail
criteria. Test methods used to verify hardware design requirements can range
from very simple steps, such as visual inspection, to elaborate test procedures
that are documented separately.
Test responsibilities include what organizations will perform the test methods
and at each stage of the product life. This allows test organizations to plan,
acquire or develop test equipment and other resources necessary to implement the
test methods for which they are responsible. Test responsibilities also
includes, what data will be collected, and how that data will be stored and
reported (often referred to as "deliverables"). One outcome of a successful test
plan should be a record or report of the verification of all design
specifications and requirements as agreed upon by all parties.
IEEE 829-1998:
a) Test plan identifier;
b) Introduction;
c) Test items;
d) Features to be tested;
e) Features not to be tested;
f) Approach;
g) Item pass/fail criteria;
h) Suspension criteria and resumption requirements;
i) Test deliverables;
j) Testing tasks;
k) Environmental needs;
l) Responsibilities;
m) Staffing and training needs;
n) Schedule;
o) Risks and contingencies;
p) Approvals.
Are you interested in
mult-player online internet games? Such as runescape and neopets?Internet
Game Online-games, tips, cheats and kids forumsAnother
good forum is the Internet Junction For Gamers IJFG.COM
Internet Junction For Gamers, Runescape Market and
More IJFG.COM Jokes, Pranks, Runescape and other cool games at IJFG.COM.
RuneScape is set in a medieval fantasy world, similar to "Guild Wars" or
"EverQuest", where players control character representations of themselves. As
with most massive multiplayer online roleplaying games (MMORPG), there is no
overall objective or end to the game. Players explore, form alliances, perform
optional tasks, and complete quests for rewards and to build character's skills.
RuneScape has often been one of
the top massive online role playing games. It is a unique game. But, with a
unique game, comes unique players. Players get bored, and then try to develop
cheats....autos or bots that will help them achieve success in their beloved
games of Runescape 2.
RuneScape is a virtual world which
is divided into two part: Members Areas and Non-Members areas. People who pay to
play (p2p), receive access to the special areas. They also have access to the
free areas. The members' places are much larger, offer "better" items for the
gameplay of rs2, and much, much more. The character that you create when you
first start playing runescape, moves around the game on foot; either by running,
or walking. Players are challenged to their utmost skills by fighting new
monsters, completing difficult quests, and manipulating marketing. As Runescape
2 is an RPG (Role playing game), there is no set path a person must take to play
rs. They can choose what to do, and when, whether it be training their
money-making skills, or fighting another player. Players usually interact with
each other by chatting through public chat, or private chat.Internet
Junction For Gamers, Runescape Market and More IJFG.COM IJFG.com was a
runescape 2 based site. They have now, however, taken another look....
Of course the king of all game
cheating websites is
trick
the trik (otherwise known as RPG Cheats Site), where you can find cheat
forums, mmorpg topsite, arcade games and any mmo game related topics.
The master of massive multiplayer
online role-playing games (MMORPG) cheats can be found at Trik.com
Trik.com; this site is one of the best today. The forum section,
Trik.com forum, originally came from IJFG.com (Internet Junction For
Gamers) , which was one of the best websites that discussed various gamers'
issues. The full name was Internet Junction For Gamers, Runescape Market and
More. This site had Jokes, Pranks, RuneScape and other cool games. RuneScape is
set in a medieval fantasy world, similar to "Guild Wars" or "EverQuest," where
players control character representations of themselves. As with most MMORPG,
there is no overall objective or end to the game. Players explore, form
alliances, perform optional tasks, and complete quests for rewards and to build
characters' skills.
Trik.com continues IJFG.com's
success, but Trik.com has more to offer. Trik Topsite can be found at
Trik Topsite; the TopSite is a great addition if you want to find the best
MMO RPG site(s) or raise your site in the rankings. Trik.com also has a
viciously competitive Arcade. If you want to be the #1 Arcade on Trik, then come
prove yourself at Trik.com arcade:
Trik arcade. Trik.com ?Trik.com/topsite ?Trik.com/forum/arcade.php
With the rising popularity of
commercial MMORPG games came the desire from ardent players of these games to
run their own servers beside the ones run by the game's creator. Since the
original server software is not usually available, the behavior of the server
has to be re-engineered. This can be done by analyzing the data stream with the
original server, or by disassembling and analyzing the client which is
available.
Ultima Online was one of the first
large MMORPGs. Due to its openness in implementation, server emulators arose
very quickly, even during the beta stage of development. The destination to
which the client connects was changeable by simply editing a text file. In beta
stage the client-server data stream was not encrypted yet. The term server
emulator became known through Ultima Online server reimplementation such as UOX,
which was the pioneer. Many forks and reimplementations followed UOX, because
its source code was released under the GNU General Public License relatively
early. RunUO is today the most widely used UO-server emulator. After RuneScape
implemented anti-cheating measures, many gamers left and started their own
private servers. The best place to discuss the private server is at
Trik- The Master of Private Server.
Another useful site is
Rune
Web ruwb.com . This site is about more serious RuneScape gold trading,
account exchange, gold for real life cash and many services. It includes tips on
how to avoid getting lured/scammed while using the marketplace. For programming,
visual basics, java, C/C++, scar and all other languages such as PHP, HTML, ASP,
Delphi. There are also sections for graphics talents, plus many cool videos and
fun stuff.
A defining moment in internet
gaming history was when a group of gamers called (hygo 7) decided to start an
ultimate game forum, which they named
hygo.com. It has the best financial backing, the friendliest game community,
and the highest quality of information. Currently Hygo.com has entered a new
phase...Hygo.com is offering the best private server game. With thousands of
members, Hygo.com is your next place to visit, as they have an amazing game with
a community and economy.
Hygo.com - The Online Adventure Game. is definitely one of the top sites you
want to join right now!
EZud is another popular site.
ezud.com. It has the best runescape bug abuse, bugs and trik.
ezud.com - The runescape bugs. is definitely one of the best sites you want
to join right now!
Contact Information
Call our office today to set up an appointment. Learn more about how we can
help you, and learn more about the other services that we can offer you. All
messages we receive will be answered as soon as possible. We look forward to
hearing from you.
- Electronic mail
- General Information:
