Test Repository provides a database of test results which fits into developers work flow and keeps track of useful information like what tests are failing, or which failures have the same backtrace.
This project provides a database of test results which can be used as part of
developer workflow to ensure/check things like:
* No commits without having had a test failure, test fixed cycle.
* No commits without new tests being added.
* What tests have failed since the last commit (to run just a subset).
* What tests are currently failing and need work.
Test results are inserted using subunit (and thus anything that can output
subunit or be converted into a subunit stream can be accepted).
A mailing list for discussion, usage and development is at https:/
Source code is maintained at https:/
CI for the project is at http://
Project information
- Maintainer:
- testrepository committers
- Driver:
- Not yet selected
- Licence:
- Apache Licence, Simplified BSD Licence
View full history Series and milestones
trunk series is the current focus of development.
All code Code
- Version control system:
- Bazaar
- Programming languages:
- python
All packages Packages in Distributions
-
testrepository source package in Xenial
Version 0.0.20-2 uploaded -
testrepository source package in Trusty
Version 0.0.18-1ubuntu1 uploaded -
testrepository source package in Sid
Version 0.0.20-8 uploaded -
testrepository source package in Precise
Version 0.0.5-1.1 uploaded -
testrepository source package in Mantic
Version 0.0.20-8 uploaded
All bugs Latest bugs reported
-
Bug #1842403: Could not import command module testrepository.commands.slowest when ‘testr slowest’
Reported -
Bug #1382579: check-neutron-dsvm-functional dies with Length too long
Reported -
Bug #1538941: "Race in testr accounting" problem in some setups
Reported -
Bug #1532109: testr list-tests --quiet is too noisy
Reported -
Bug #1505927: branch coverage is either unsupported or undocumented
Reported
