53901fb23d
Release notes are version independent, so remove version/release values. We've found that projects now require the service package to be installed in order to build release notes, and this is entirely due to the current convention of pulling in the version information. Release notes should not need installation in order to build, so this unnecessary version setting needs to be removed. This is needed for new release notes publishing, see I56909152975f731a9d2c21b2825b972195e48ee8 and the discussion starting at http://lists.openstack.org/pipermail/openstack-dev/2017-November/124480.html . Change-Id: If85d6e137edff3bf8a764dd517a3528cc813f744 |
||
---|---|---|
coverage2sql | ||
doc/source | ||
etc | ||
releasenotes | ||
tools | ||
.coveragerc | ||
.gitignore | ||
.gitreview | ||
.mailmap | ||
.testr.conf | ||
CONTRIBUTING.rst | ||
HACKING.rst | ||
LICENSE | ||
MANIFEST.in | ||
README.rst | ||
babel.cfg | ||
requirements.txt | ||
setup.cfg | ||
setup.py | ||
test-requirements.txt | ||
tox.ini |
README.rst
Team and repository tags
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.
- Free software: Apache license
- Documentation: http://docs.openstack.org/developer/coverage2sql
- Source: http://git.openstack.org/cgit/openstack/coverage2sql
- Bugs: http://bugs.launchpad.net/coverage2sql
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/