Tooling for converting coverage data into a SQL DB
Go to file
Doug Hellmann f5a1c60493 fix tox python3 overrides
We want to default to running all tox environments under python 3, so
set the basepython value in each environment.

We do not want to specify a minor version number, because we do not
want to have to update the file every time we upgrade python.

We do not want to set the override once in testenv, because that
breaks the more specific versions used in default environments like
py35 and py36.

Change-Id: I66d77a977b76118d3a7b74f1f5b238370b43a38d
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
2018-09-26 18:47:47 -04:00
coverage2sql Add files table 2017-03-08 18:39:32 +09:00
doc/source replace http with https 2018-09-12 16:37:00 -06:00
etc Add unit tests and remove oslo_db 2016-11-11 11:33:43 +09:00
releasenotes Remove setting of version/release from releasenotes 2017-11-16 22:08:23 +01:00
tools Prepare for using standard python tests 2017-02-02 12:11:19 +00:00
.coveragerc Omit unit test files from coverage 2016-11-11 19:40:27 +09:00
.gitignore Switch to use stestr instead of os-testr 2017-12-16 17:45:42 +09:00
.gitreview Initial Cookiecutter Commit. 2016-04-19 12:24:29 +09:00
.mailmap Initial Cookiecutter Commit. 2016-04-19 12:24:29 +09:00
.stestr.conf Switch to use stestr instead of os-testr 2017-12-16 17:45:42 +09:00
.zuul.yaml Use openstack-tox-cover template 2018-09-09 06:07:27 +02:00
CONTRIBUTING.rst replace http with https 2018-09-12 16:37:00 -06:00
HACKING.rst Update url in HACKING.rst 2018-09-12 16:49:35 -06:00
LICENSE Initial Cookiecutter Commit. 2016-04-19 12:24:29 +09:00
MANIFEST.in Add unit tests and remove oslo_db 2016-11-11 11:33:43 +09:00
README.rst replace http with https 2018-09-12 16:37:00 -06:00
babel.cfg Initial Cookiecutter Commit. 2016-04-19 12:24:29 +09:00
requirements.txt Update requirements 2017-04-27 16:53:43 +09:00
setup.cfg turn on warning-is-error in documentation build 2017-06-27 08:46:34 +00:00
setup.py Update requirements 2017-04-27 16:53:43 +09:00
test-requirements.txt Switch to use stestr instead of os-testr 2017-12-16 17:45:42 +09:00
tox.ini fix tox python3 overrides 2018-09-26 18:47:47 -04:00

README.rst

Team and repository tags

image

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.

Usage

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.

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.

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.

TODO

To see the TODO, go to the launchpad site:

ChangeLog

To see the release notes go here: https://docs.openstack.org/releasenotes/coverage2sql/