[merge] doc testing of exceptions
Robert Collins
robertc at robertcollins.net
Thu Jul 12 10:28:02 BST 2007
On Thu, 2007-07-12 at 19:12 +1000, Martin Pool wrote:
> Robert gave some feedback to Marius previously on how to test
> exceptions. This adds (my understanding of) it to the developer
> guide.
+
+.. TODO: Should have some explanation of why you'd want things in
+.. branch.conf.
+
I don't think we should put TODO's in the user manual. Perhaps you could
file a bug instead which will be visible and queryable.
+
+In some cases blackbox tests will also want to check error reporting.
But
+it can be difficult to provoke every error through the commandline
+interface, so those tests are only done as needed -- eg in response to
a
+particular bug or if the error is reported in an unusual way(?)
+
I think its worth noting that blackbox tests are not testing the error
formatting because that is tested separately. So the thing for blackbox
tests is to try to exercise ways in which the code *within builtins.py*
can break, not code deeper down.
One thing that seems weird about your diff to me is we already have
testing documentation in HACKING - why is your new content titled
+Testing Bazaar
+--------------
?
+1 conditional
-Rob
--
GPG key available at: <http://www.robertcollins.net/keys.txt>.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20070712/d9d0caf1/attachment.pgp
More information about the bazaar
mailing list