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.
 
 
 
 
Masayuki Igawa 551c604e22 Omit unit test files from coverage 5 years ago
coverage2sql Add get_coverage() 5 years ago
doc/source Initial Cookiecutter Commit. 5 years ago
etc Add unit tests and remove oslo_db 5 years ago
releasenotes Add releasenote 5 years ago
.coveragerc Omit unit test files from coverage 5 years ago
.gitignore Add adding data feature 5 years ago
.gitreview Initial Cookiecutter Commit. 5 years ago
.mailmap Initial Cookiecutter Commit. 5 years ago
.testr.conf Initial Cookiecutter Commit. 5 years ago
CONTRIBUTING.rst Initial Cookiecutter Commit. 5 years ago
HACKING.rst Initial Cookiecutter Commit. 5 years ago
LICENSE Initial Cookiecutter Commit. 5 years ago
MANIFEST.in Add unit tests and remove oslo_db 5 years ago
README.rst Add usage to README and make coverage file positional 5 years ago
babel.cfg Initial Cookiecutter Commit. 5 years ago
requirements.txt Add unit tests and remove oslo_db 5 years ago
setup.cfg Add migration and shell 5 years ago
setup.py Initial Cookiecutter Commit. 5 years ago
test-requirements.txt Add unit tests and remove oslo_db 5 years ago
tox.ini Add unit tests and remove oslo_db 5 years ago

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