User: fleury
Date: 00/11/17 11:54:35
Modified: developers jboss-test.html
Log:
name edits
Revision Changes Path
1.5 +12 -2 newsite/developers/jboss-test.html
Index: jboss-test.html
===================================================================
RCS file: /products/cvs/ejboss/newsite/developers/jboss-test.html,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- jboss-test.html 2000/11/17 19:37:34 1.4
+++ jboss-test.html 2000/11/17 19:54:34 1.5
@@ -18,8 +18,18 @@
<td
class="newsheader"><b>TestSuite</b></td>
</tr>
<tr>
- <td class="newsbody"><font
face="Myriad Web,Arial">Systematically and thoroughly testing the jboss development
has become a pressing need for the organization. There were several independent tests
done in jboss but it is the first time we spin off such a project. The modular growth
of jboss2.0 puts new demands on the testing infrastructure. A formalized approach to
software testing is being applied in JCTS, the unit tests for jboss. Under the
leadership of <b>Peter Braswell</b> it aims to become the Quality Assurance and
Conformity arm of jboss. It is important to make sure all the i's are dotted and t's
crossed in order to insure that the EJB specification has been faithfully
implemented.</font>
- <p><font face="Myriad
Web,Arial">Internaly to jboss, the development team will use JCTS to make sure that
things are implemented correctly and that the changes commited during the day do not
break the server. It will make sure that no functionality has been overlooked and
missed. We need to make sure that new features do not interfere with old ones,
something that is going to get harder and harder to detect at the code level as the
modular base of jboss 2.0 grows.</font></p>
+
+ <td class="newsbody"><font face="Myriad Web,Arial">Systematically and
+ thoroughly testing the jboss development has become a pressing need
+ for the organization. There were several independent tests done in
+ jboss but it is the first time we spin off such a project. The modular
+ growth of jboss2.0 puts new demands on the testing infrastructure.
+ A formalized approach to software testing is being applied in JCTS,
+ the unit tests for jboss. It aims to become the Quality Assurance
+ and Conformity arm of jboss. It is important to make sure all the
+ i's are dotted and t's crossed in order to insure that the EJB
specification
+ has been faithfully implemented.</font>
+ <p><font face="Myriad Web,Arial">Internaly to jboss, the development
team will use JCTS to make sure that things are implemented correctly and that the
changes commited during the day do not break the server. It will make sure that no
functionality has been overlooked and missed. We need to make sure that new features
do not interfere with old ones, something that is going to get harder and harder to
detect at the code level as the modular base of jboss 2.0 grows.</font></p>
<p><font face="Myriad
Web,Arial">JCTS is built on top of a testing framework (JUnit) that makes it easy to
add and run tests but most of all to get pretty clear feedback as to the outcome. It
will be used to gate the release process and to bless the code as
release-worthy.</font></p>
<p><font face="Myriad
Web,Arial">Recently and with the stabilization of jBoss under way, the TestSuite has
become a scalability, stability, locking detection framework. We ship a series
of tests, benchmarks, and stress-tests that are know to max the biggest hardware out
there.</font></td>
</tr>
