Test Plan Standards
Rohinee Mohindroo
try IEEE standards
Ronald Albuquerque wrote:
>
> Hello folks,
>
> Are there any publicly accessible standards
> on writing a test plan ? We're looking to
> publish a "What a Test Plan should contain"
> type document.
>
> Any information is much appreciated.
>
> cheers.
>
> --ronnie
> --
> --------------------------------------------------------------------------
> Ronald Albuquerque | NEON Software, Inc. | Mail: ral...@neonsoft.com
> Sr. Software Engineer | 7400 E Orchard Rd, #230 | Ph: 303-486-9333
> C++ Test Development | Englewood, CO 80111 | Fax: 303-694-3885
> --------------------------------------------------------------------------
LogicWare Corp
Two sources:
Testing Computer Software (book) - Author ???
IEEE software standards
LogicWare Corporation
phone (201) 244-0587
fax (201) 244-0691
Ronald Albuquerque <r...@netcom.com> wrote in article
<rjaE2D...@netcom.com>...
cvi...@btree.com
> r...@netcom.com (Ronald Albuquerque) writes:
> Hello folks,
>
> Are there any publicly accessible standards
> on writing a test plan ? We're looking to
> publish a "What a Test Plan should contain"
> type document.
>
> Any information is much appreciated.
>
>>>>
You can get it at http://www.computer.org/
I recommned their complete standards collection:
Software Engineering Standards Collection: 1994 Edition
1994. ISBN 1-55937-442-X.
Catalog # ST01064 — $176.00 Members / $207.00 List
|==================================================================|
| Carlos Vicens | B-Tree Verification Systems, Inc. |
| cvi...@BTREE.COM | 5929 Baker Rd, Suite 475 |
| (VOICE) 612-930-4135 | Minnetonka, MN 55345-5955 |
| (FAX) 612-936-2187 | |
|==================================================================|
GTredgold
hi ronnie
i could provide you with my test plan/strategy template, its kind of a
fill in the blanks test plan.
i have several years exp opf large systems testing, and also asa project
manager i used it to control my own test managers
if you are interested email me
Sylvain Coulombe
Ronald Albuquerque wrote:
>
> Hello folks,
>
> Are there any publicly accessible standards
> on writing a test plan ? We're looking to
> publish a "What a Test Plan should contain"
> type document.
>
> Any information is much appreciated.
>
>
> --ronnie
> --
> --------------------------------------------------------------------------
> Ronald Albuquerque | NEON Software, Inc. | Mail: ral...@neonsoft.com
> Sr. Software Engineer | 7400 E Orchard Rd, #230 | Ph: 303-486-9333
> C++ Test Development | Englewood, CO 80111 | Fax: 303-694-3885
> --------------------------------------------------------------------------
You may want to take a look at MIL-STD-498. I know that there is a
commercial equivalent to this standard, but I do not know where to get
it. MIL-STD-498 can be obtained at
http://stsc.hill.af.mil/~doc/index.html
This standard covers more than just the testing portion, it addressed
the entire software development cycle. It also provides Data Item
Descriptions (templates in plain english) than suggest contents for
something like 22 documents that should flow out of the software
development cycle. Among these, you'll find templetes for Test Plans,
Test Descriptions, Test Reports, etc. There is more in those than
anyone usually needs, so it is a good place to start and take what you
think is appropriate in your specific environment.
Sylvain Coulombe
coul...@capitalnet.com
Cem Kaner
On Fri, 13 Dec 1996 19:48:26 GMT, r...@netcom.com (Ronald Albuquerque)
wrote:
>Are there any publicly accessible standards
>on writing a test plan ? We're looking to
>publish a "What a Test Plan should contain"
>type document.
>--------------------------------------------------------------------------
IEEE Standard 829 is a valuable tool for defining the types of
information that you MIGHT include in a test plan, but I've found that
many test plans derived from 829 tend to be bloated with corporate,
project, and political information.
829 provides an excellent framework if you have a customer who demands
(and will pay for) a formal test plan as part of the product. It gives
you a shared vocabulary and a shared set of acceptance standards.
On the other hand, if you are writing a test plan strictly for
in-house use, then you might prefer something that focuses on
organizing your technical testing strategy. I tend to create binders
that include boundary tables, data relationship tables, parameter
combination tables, and standardized test matrices. These are terse
documents that point me to the critical issues that I want to test. I
haven't yet seen a template that fully structures this collection of
material.
For the testing project (budget, time, etc.), I've posted some notes
on my web page -- check out www.kaner.com/negotiate.htm for a paper
that I gave at Quality Week last year on this topic.
- Cem Kaner
Shel Prince
IEEE publishes a set of standards on this subject. They have Test
Plan, Test Design and Test Case Specification standards. The also have
Software Quality Assurance Plan (SQAP) standard and guideline. I have
seen these documents for sale at a bookstore, or they are available
through IEEE. Sorry, I don't have their contact number of website with
me right now. The bookstore that had these is Computer Literacy, and
they are at www.clbooks.com (I think) Hope this helps. -- shel
Sylvain Coulombe wrote:
>
> Ronald Albuquerque wrote:
> >
> > Hello folks,
> >
> > Are there any publicly accessible standards
> > on writing a test plan ? We're looking to
> > publish a "What a Test Plan should contain"
> > type document.
> >
Burt Gearhart
Checkout:
http://www.acomtech.com/act/testplan.html
_______________________________________
Burt Gearhart bu...@metronet.com /__________________________________
Applied Computer Technology 972.271.6550 3270, 5250, RJE, APPC, APPN
Garland, TX USA FAX: 972.271.6466 SNA & TCP/IP
http://www.acomtech.com/act Testing for Tomorrow...Today!
_____________________________ Conformance, Load/Stress with SDTF and ITF
/____________________________________________