Changes between Version 2 and Version 3 of ReportingBugs

Timestamp:

Jul 27, 2007, 12:58:19 AM (15 years ago)

Author:

Peter Dimov

Comment:

--

ReportingBugs

@@ -9 +9 @@
 The maintainers of the Boost component affected by the bug will appreciate it if you already have an idea how to fix it. It's best if you submit a patch, as explained [http://www.boost.org/more/bugs.htm here].
 
-It's even more helpful if you submit a new unit test. This guarantees that the bug stays fixed.
+It's even more helpful if you submit a new test. This guarantees that the bug stays fixed.
 
-== Submitting a Unit Test ==
+== Submitting a Test ==
 
-Creating an unit test is easy. We'll illustrate this with an [http://lists.boost.org/boost-users/2007/07/29648.php example] taken from the [http://lists.boost.org/boost-users/ boost-users] mailing list:
+Creating a test is easy. We'll illustrate this with an [http://lists.boost.org/boost-users/2007/07/29648.php example] taken from the [http://lists.boost.org/boost-users/ boost-users] mailing list:
 
   The following code using Lambda with vector iterators compiles without complaint:
@@ -42 +42 @@
   that I didn't see documented somewhere?
 
-Here's the unit test that you, as the hypothetical reporter of the above bug, can submit as an attachment to the new ticket:
+Here's the test that you, as the hypothetical reporter of the above bug, can submit as an attachment to the new ticket:
 
 {{{
@@ -69 +69 @@
 }}}
 
-Note that even though the bug report only states that the code doesn't compile, the unit test actually tests whether the code, when compiled, actually does what it's expected to do. This may seem trivial, but it does help. Be sure to not forget the `return boost::report_errors()` statement at the end of `main`.
+Note that even though the bug report only states that the code doesn't compile, the test checks whether the code, when compiled, actually does what it's expected to do. This may seem trivial, but it does help. Be sure to not forget the `return boost::report_errors()` statement at the end of `main`.
 
-Thank you in advance for your bug reports and unit tests!
+Thank you in advance for your bug reports and tests!