openstack/coverage2sql
Code Issues Proposed changes
Tooling for converting coverage data into a SQL DB
41 Commits 1 Branch 0 Tags 737 KiB
Python 95.7%
Shell 3.4%
Mako 0.9%
20f1fb6f10
Go to file
Masayuki Igawa 20f1fb6f10
Update docs theme 
This commit updates the docs theme to the new one. The new theme is the
standard of the openstack document. There is no reason to avoid to use
it.

Change-Id: If17ce35bd2ba50c3e1ae6e1567dcbe4be59d5189
2017-06-05 13:50:38 +09:00
coverage2sql Add files table 2017-03-08 18:39:32 +09:00
doc/source Update docs theme 2017-06-05 13:50:38 +09:00
etc Add unit tests and remove oslo_db 2016-11-11 11:33:43 +09:00
releasenotes Add files table 2017-03-08 18:39:32 +09: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 Add adding data feature 2016-04-21 16:40:45 +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
.testr.conf Initial Cookiecutter Commit. 2016-04-19 12:24:29 +09:00
babel.cfg Initial Cookiecutter Commit. 2016-04-19 12:24:29 +09:00
CONTRIBUTING.rst Initial Cookiecutter Commit. 2016-04-19 12:24:29 +09:00
HACKING.rst Initial Cookiecutter Commit. 2016-04-19 12:24:29 +09: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 Fix coverage2sql-db-manage usage document 2017-02-03 16:50:00 +09:00
requirements.txt Update requirements 2017-04-27 16:53:43 +09:00
setup.cfg Add py3.5 support in setup.cfg 2017-04-06 09:38:42 +00:00
setup.py Update requirements 2017-04-27 16:53:43 +09:00
test-requirements.txt Update docs theme 2017-06-05 13:50:38 +09:00
tox.ini Add py36 to tox.ini 2017-02-03 12:42:19 +09: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: http://docs.openstack.org/releasenotes/coverage2sql/