opendev/subunit2sql
Code Issues Proposed changes
Tooling for converting subunit streams into a SQL DB
31 Commits 1 Branch 31 Tags 6.1 MiB
Python 99.4%
Shell 0.5%
Mako 0.1%
9076f715b8
Go to file
Matthew Treinish 9076f715b8 Add a .gitreview file 
Since subunit2sql was adopted by openstack-infra code submissions and
reviews will be done in openstack gerrit. This commit adds a
.gitreview file to subunit2sql, so that by default the git review
command will point to the right location for subunit2sql.

Change-Id: I043cbd59fb7c3e83de2dfe8922b0ab96c56cd37f
2014-07-12 12:48:23 -04:00
doc/source Add sphinx docs 2014-06-24 16:21:38 -04:00
subunit2sql Add unit tests for ReadSubunit helper methods 2014-06-25 11:56:23 -04:00
.gitignore Update project packaging 2014-06-24 15:50:36 -04:00
.gitreview Add a .gitreview file 2014-07-12 12:48:23 -04:00
.testr.conf Add basic unit tests 2014-06-24 20:14:18 -04:00
alembic.ini Initial commit 2014-06-12 23:59:00 -04:00
LICENSE Initial commit 2014-06-12 23:59:00 -04:00
openstack-common.conf Initial commit 2014-06-12 23:59:00 -04:00
README.rst Cleanup the readme 2014-06-24 16:00:13 -04:00
requirements.txt Add basic unit tests 2014-06-24 20:14:18 -04:00
setup.cfg Release subunit2sql-0.1 2014-07-06 14:27:34 -04:00
setup.py Initial commit 2014-06-12 23:59:00 -04:00
test-requirements.txt Update requirements files 2014-06-24 16:26:50 -04:00
TODO.rst Update the TODO file again 2014-07-09 15:55:41 -04:00
tox.ini Add basic unit tests 2014-06-24 20:14:18 -04:00

README.rst

subunit2SQL README

subunit2SQL like it's name implies is a tool used for converting subunit streams to data in a SQL database. The motivation is that for multiple distributed test runs that are generating subunit output it is useful to store the results in a unified repository. This is the motivation for the testrepository project which does a good job for centralizing the results from multiple test runs.

However, imagine something like the OpenStack CI system where the same basic test suite is normally run several hundreds of times a day. To provide useful introspection on the data from those runs and to build trends over time the test results need to be stored in a format that allows for easy querying. Using a SQL database makes a lot of sense for doing this.

subunit2SQL uses alembic migrations to setup a DB schema that can then be used by the subunit2sql binary to parse subunit streams and populate the DB. Additionally, it provides a DB API that can be used to query information from the results stored to build other tooling.