openstack
/
coverage2sql
Code Issues Proposed changes
Tooling for converting coverage data into a SQL DB
96 Commits 1 Branch 0 Tags 705 KiB
Python 95.7%
Shell 3.4%
Mako 0.9%
Go to file
Andreas Jaeger e80d1be437 Update to hacking 3.0 
Hacking 3.0 was just released with minor changes, update to the new
version.

Change-Id: I8297a152273c5accda885df64ccedd247994076c
 		2020-03-30 17:40:08 +02:00
coverage2sql Update hacking for Python3 2020-03-28 10:47:17 +01:00
doc [ussuri][goal] Drop python 2.7 support and testing 2020-02-03 18:50:34 +00:00
etc Remove unused config entries from sample config 2019-04-17 15:47:06 +09:00
releasenotes [ussuri][goal] Drop python 2.7 support and testing 2020-02-03 18:50:34 +00: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 Ignore *.db file from git repo 2019-04-17 15:40:38 +09:00
.gitreview OpenDev Migration Patch 2019-04-19 19:36:21 +00: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 [ussuri][goal] Drop python 2.7 support and testing 2020-02-03 18:50:34 +00: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 Use opendev repository 2019-04-23 17:16:38 +08:00
babel.cfg Initial Cookiecutter Commit. 2016-04-19 12:24:29 +09:00
bindep.txt Fix gate error "mysqladmin: command not found" 2019-07-17 04:34:45 +00:00
requirements.txt Update requirements 2017-04-27 16:53:43 +09:00
setup.cfg [ussuri][goal] Drop python 2.7 support and testing 2020-02-03 18:50:34 +00:00
setup.py Update requirements 2017-04-27 16:53:43 +09:00
test-requirements.txt Update to hacking 3.0 2020-03-30 17:40:08 +02:00
tox.ini Update hacking for Python3 2020-03-28 10:47:17 +01: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.

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.

TODO

To see the TODO, go to the launchpad site:

ChangeLog

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