Go to file

Matthew Treinish f395a2b213 Store counts for runs and tests

This commit adds count updates to both the run and test tables.
Before this commit the counts of test status in the run table and
test tables weren't ever used.

2014-06-16 11:02:21 -04:00

subunit2sql

Store counts for runs and tests

2014-06-16 11:02:21 -04:00

.gitignore

Initial commit

2014-06-12 23:59:00 -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

Initial commit

2014-06-12 23:59:00 -04:00

requirements.txt

Initial commit

2014-06-12 23:59:00 -04:00

setup.cfg

Initial commit

2014-06-12 23:59:00 -04:00

setup.py

Initial commit

2014-06-12 23:59:00 -04:00

test-requirements.txt

Initial commit

2014-06-12 23:59:00 -04:00

TODO.rst

Store counts for runs and tests

2014-06-16 11:02:21 -04:00

tox.ini

Initial commit

2014-06-12 23:59:00 -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.

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. SQL databases make 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. Additional it provides a DB API that can be used to query information from the results stored to build other tooling.