clarify the status of ./waf --regression removal
authorTom Henderson <tomh@tomh.org>
Mon, 08 Nov 2010 11:36:26 -0800
changeset 6652 2d8de9b3be74
parent 6651 4bd42b7fbb3b
child 6653 d06d7b84d8b4
clarify the status of ./waf --regression removal
CHANGES.html
RELEASE_NOTES
--- a/CHANGES.html	Mon Nov 01 12:23:07 2010 -0400
+++ b/CHANGES.html	Mon Nov 08 11:36:26 2010 -0800
@@ -49,7 +49,11 @@
 <h2>Changes to build system:</h2>
 <ul>
 <li><b>Regression tests are no longer run using waf</b>
-<p>All regression testing is now being done in test.py.  As a result, reference traces are no longer needed in ns-3 to perform regression testing.
+<p>All regression testing is now being done in test.py.  As a result, a 
+separate reference trace repository is no longer needed to perform 
+regression tests.  Tests that require comparison against known good traces
+can still be run from test.py.  The --regression option for waf has been
+removed.
 </p>
 </ul>
 
--- a/RELEASE_NOTES	Mon Nov 01 12:23:07 2010 -0400
+++ b/RELEASE_NOTES	Mon Nov 08 11:36:26 2010 -0800
@@ -38,6 +38,15 @@
      will allow an initial call to SetPosition () (before any waypoints
      have been added) to be treated as the first waypoint.
 
+   - Regression testing is now completely performed within test.py
+     rather than a separate "./waf --regression" that consults
+     reference traces in the ns-3.x-ref-traces directory.  In most
+     cases, the example programs whose traces were included in 
+     ns-3.x-ref-traces have a corresponding test called from the
+     test.py program.  It is still possible to write trace-based
+     regression tests but they are now called from the test.py
+     program.
+
 Bugs fixed
 ----------
 The following lists many of the bugs fixed or small feature additions