Tooling for converting coverage data into a SQL DB
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Le Hou 9f1e5b4adf Use opendev repository 3 weeks ago
coverage2sql Add metadata column to coverage table 1 month ago
doc/source Use opendev repository 3 weeks ago
etc Remove unused config entries from sample config 1 month ago
releasenotes Remove setting of version/release from releasenotes 1 year ago
tools Prepare for using standard python tests 2 years ago
.coveragerc Omit unit test files from coverage 2 years ago
.gitignore Ignore *.db file from git repo 1 month ago
.gitreview OpenDev Migration Patch 4 weeks ago
.mailmap Initial Cookiecutter Commit. 3 years ago
.stestr.conf Switch to use stestr instead of os-testr 1 year ago
.zuul.yaml Dropping the py35 testing 3 weeks ago
CONTRIBUTING.rst replace http with https 8 months ago
HACKING.rst Update url in HACKING.rst 8 months ago
LICENSE Initial Cookiecutter Commit. 3 years ago Add unit tests and remove oslo_db 2 years ago
README.rst Use opendev repository 3 weeks ago
babel.cfg Initial Cookiecutter Commit. 3 years ago
requirements.txt Update requirements 2 years ago
setup.cfg Dropping the py35 testing 3 weeks ago Update requirements 2 years ago
test-requirements.txt Introduce doc8 1 month ago
tox.ini Dropping the py35 testing 3 weeks ago


Team and repository tags


coverage2sql README

Command to Read a coverage file and put the data in a SQL database

coverage2sql is a tool for storing data of test coverage into a SQL database. With using this tool, you can store time series coverage data and analyze it if your coverage rate is down.


DB Setup

The usage of coverage2sql is split into 2 stages. First you need to prepare a database with the proper schema; coverage2sql-db-manage should be used to do this. The utility requires db connection info which can be specified with a config file. Obviously the sql connector type, user, password, address, and database name should be specific to your environment. coverage2sql-db-manage will use alembic to setup the db schema. You can run the db migrations with a config file:

coverage2sql-db-manage --config-file etc/coverage2sql.conf upgrade head

This will bring the DB schema up to the latest version for coverage2sql.


Once you have a database setup with the proper database schema you can then use the coverage2sql command to populate the database with data from your test coverage file. coverage2sql takes in a .coverage file through by passing it file paths as positional arguments to the script at this moment.

For example:

coverage2sql --config-file etc/coverage2sql.conf coverage2sql .coverage

There are several options for running coverage2sql, they can be listed with:

coverage2sql --help

The only required option is --database-connection. The options can either be used on the CLI, or put in a config file. If a config file is used you need to specify the location on the CLI.


To see the TODO, go to the launchpad site:


To see the release notes go here: