openstack/coverage2sql
Code Issues Proposed changes
Tooling for converting coverage data into a SQL DB
13 Commits 1 Branch 0 Tags 737 KiB
Python 95.7%
Shell 3.4%
Mako 0.9%
a760eb18ad
Go to file
Masayuki Igawa a760eb18ad Add test_type param to create_coverage()
2016-11-07 16:48:38 +09:00
coverage2sql Add test_type param to create_coverage() 2016-11-07 16:48:38 +09:00
doc/source Initial Cookiecutter Commit. 2016-04-19 12:24:29 +09:00
.coveragerc Initial Cookiecutter Commit. 2016-04-19 12:24:29 +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 Initial Cookiecutter Commit. 2016-04-19 12:24:29 +09:00
README.rst Add usage to README and make coverage file positional 2016-10-20 16:40:14 +09:00
requirements.txt Remove oslo_db dependency 2016-11-07 16:46:09 +09:00
setup.cfg Add migration and shell 2016-04-19 19:00:55 +09:00
setup.py Initial Cookiecutter Commit. 2016-04-19 12:24:29 +09:00
test-requirements.txt Add migration and shell 2016-04-19 19:00:55 +09:00
tox.ini Initial setup 2016-04-19 13:55:22 +09:00

README.rst

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 on the command or 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 the command:

coverage2sql-db-manage --database-connection mysql://coverage:pass@127.0.0.1/coverage upgrade head

or 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.

Features

  • TODO: .coverage file through stdin