<div dir="ltr"><div class="gmail_quote">
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">
<div class="im">It's pretty standard for testing documents to be in MS Word at my<br>workplace. This includes both high-level documents that are primarily<br>used by non-technical people and detailed test plans that are only<br>
used by engineers.<br><br></div></blockquote>
<div>So my company is the only one with the lame testing documents, weee!</div>
<div> </div>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">
<div class="im"><span id=""></span>Occasionally a company will allow the engineers to do all the test<br>plans on a Wiki, but I've only heard of that once.<br><br>There are a couple of tools designed to be editable or readable both<br>
by technical and non-technical people. Like FIT/Fitnesse, but I'm not<br>sure that would exactly meet your needs.<br><br></div></blockquote>
<div>I just posted why we are NOT using PyFit.</div>
<div> </div>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">
<div class="im"><span id=""></span>There is actually an standard (IEEE 829<br><a href="http://en.wikipedia.org/wiki/IEEE_829" target="_blank">http://en.wikipedia.org/wiki/IEEE_829</a>) covering various types of<br>artifacts to plan testing and report testing results. It tends to be<br>
*very* heavy weight though.<br><br></div>(Forgot to send to list. Sorry for the spam Yoav)<br>=====<br>--Ryan E. Freckleton</blockquote>
<div>np</div></div></div>