aboutsummaryrefslogtreecommitdiffstats
path: root/test.py
Commit message (Collapse)AuthorAgeFilesLines
* Ran update-copyright.py.W. Trevor King2012-02-161-10/+10
|
* Run update_copyright.py.W. Trevor King2011-05-251-0/+1
|
* Bumped to version 1.0.01.0.0Chris Ball2011-01-081-1/+1
|
* Ran update_copyright.py.W. Trevor King2010-10-211-1/+1
|
* Ran update_copyright.pyW. Trevor King2010-06-221-12/+13
|
* Add version information to test.py stderr for easier error reproductionW. Trevor King2010-01-291-0/+2
|
* Add --help, --quiet options to test.py.W. Trevor King2010-01-271-33/+43
| | | | | | | | | | | | | | | | | | | | Fixes Ben's "unintuitive test.py interface" bug: Date: Wed, 27 Jan 2010 14:09:14 +1100 From: Ben Finney Subject: [Be-devel] Re: Test suite on Trevor's development branch ... > $ python ./test.py -q > > ---------------------------------------------------------------------- > Ran 0 tests in 0.000s > > OK Running a Python unittest-capable test suite with "-q" should run it in "quiet" mode, where progress is indicated by single characters along a lone, and only failures and errors are reported. ...
* Updated copyright informationW. Trevor King2010-01-011-1/+17
|
* Better import error messages in test.pyW. Trevor King2009-12-311-1/+5
|
* Converted libbe.storage.vcs.base to new Storage format.W. Trevor King2009-12-131-2/+5
|
* Added libbe.command.base (with Command class) and moved list command to new ↵W. Trevor King2009-12-121-4/+6
| | | | format.
* Reworked test.py to handle deeper directory structureW. Trevor King2009-12-081-40/+65
|
* Added libbe.TESTING (defaults to False).W. Trevor King2009-12-031-0/+2
| | | | | | | | | | | | | | | | | | | | This flag allows us to skip unittest and testsuite declaration if we woln't need them. It speeds up simple be calls a suprising amount. With Testing=True (the old behavior): wking@thor:be.wtk$ time ./be > /dev/null real 0m0.393s user 0m0.340s sys 0m0.048s With TESTING=False (the new behavior): be.wtk$ time ./be > /dev/null real 0m0.216s user 0m0.152s sys 0m0.064s This adjustment was inspired by Jakub Wilk's Debian bug: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=559295
* test.py now uses unittest.TestSuite 'suite' in becommands if present.W. Trevor King2009-11-281-1/+4
| | | | | | Such 'suite' instances have been required for libbe submodules. This will allow becommands to test themselves more thoroughly than they could with only doctests.
* Adjusted test.py to use an installed vcs by default.W. Trevor King2009-11-201-4/+5
| | | | | | | | | Protects agaist the off chance that the user doesn't have Arch (tla) installed ;). Changed Arch.name from "Arch" to "arch" so that each VCSs .name matches the module name. This allows us to use vcs.VCS_ORDER (a list of module names) to set up the allowed values of BugDir.vcs_name.
* Fixed some erroneous "no test suite" messages in test.py.W. Trevor King2008-12-011-5/+6
|
* Added more helpful error message for libbe modules missing test suites.W. Trevor King2008-11-281-0/+2
|
* Another major rewrite. Now BugDir, Bug, and Comment are more distinct.W. Trevor King2008-11-211-19/+19
| | | | | | | | | | | | | | | I pushed a lot of the little helper functions into the main classes, which makes it easier for me to keep track of what's going on. I'm now at the point where I can run through `python test.py` with each of the backends (by changing the search order in rcs.py _get_matching_rcs) without any unexpected errors for each backend (except Arch). I can also run `test_usage.sh` without non-Arch errors either. However, don't consider this a stable commit yet. The bzr backend is *really*slow*, and the other's aren't blazingly fast either. I think I'm rewriting the entire database every time I save it :p. Still, it passes the checks. and I don't like it when zounds of changes build up.
* Major rewrite of RCS backends. RCS now represented as a class.W. Trevor King2008-11-181-18/+29
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Lots of changes and just one commit. This started with bug dac91856-cb6a-4f69-8c03-38ff0b29aab2, when I noticed that new bugs were not being added appropriately with the Git backend. I'd been working with Git trouble before with bug 0cad2ac6-76ef-4a88-abdf-b2e02de76f5c, and decided things would be better off if I just scrapped the current RCS architecture and went to a more object oriented setup. So I did. It's not clear how to add support for an RCS backend: * Create a new module that - defines an inheritor of rsc.RCS, overriding the _rcs_*() methods - provide a new() function for instantizating the new class - defines an inheritor of rcs.RCStestCase, overiding the Class attribute - defines 'suite' a unittest.TestSuite testing the module * Add your new module to the rest in rcs._get_matching_rcs() * Add your new module to the rest in libbe/tests.py Although I'm not sure libbe/tests.py is still usefull. The new framework clears out a bunch of hackery that used to be involved with supporting becommands/diff.py. There's still room for progress though. While implementing the new verision, I moved the testing framework over from doctest to a doctest/unittest combination. Longer tests that don't demonstrate a function's usage should be moved to unittests at the end of the module, since unittest has better support for setup/teardown, etc. The new framework also revealed some underimplented backends, most notably arch. These backends have now been fixed. I also tweaked the test_usage.sh script to run through all the backends if it is called with no arguments. The fix for the dac bug turned out to be an unflushed file write :p.
* * use python2.4/2.5 compatible import of ElementTreeW. Trevor King2008-11-131-0/+10
| | | | | * catch Popen() calls to missing VCS binaries * test.py should only test installed backends
* Exit with a nonzero status if the tests fail.Marien Zwart2006-04-051-5/+15
|
* Added unit testing frameworkAaron Bentley2005-03-111-0/+20