OpenDev Migration Patch
This commit was bulk generated and pushed by the OpenDev sysadmins as a part of the Git hosting and code review systems migration detailed in these mailing list posts: http://lists.openstack.org/pipermail/openstack-discuss/2019-March/003603.html http://lists.openstack.org/pipermail/openstack-discuss/2019-April/004920.html Attempts have been made to correct repository namespaces and hostnames based on simple pattern matching, but it's possible some were updated incorrectly or missed entirely. Please reach out to us via the contact information listed at https://opendev.org/ with any questions you may have.
|4 hours ago|
|coverage2sql||2 years ago|
|doc/source||7 months ago|
|etc||2 years ago|
|releasenotes||1 year ago|
|tools||2 years ago|
|.coveragerc||2 years ago|
|.gitignore||1 year ago|
|.gitreview||4 hours ago|
|.mailmap||3 years ago|
|.stestr.conf||1 year ago|
|.zuul.yaml||7 months ago|
|CONTRIBUTING.rst||7 months ago|
|HACKING.rst||7 months ago|
|LICENSE||3 years ago|
|MANIFEST.in||2 years ago|
|README.rst||7 months ago|
|babel.cfg||3 years ago|
|requirements.txt||2 years ago|
|setup.cfg||3 weeks ago|
|setup.py||2 years ago|
|test-requirements.txt||1 year ago|
|tox.ini||3 months ago|
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.
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.
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:
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.
To see the TODO, go to the launchpad site:
To see the release notes go here: https://docs.openstack.org/releasenotes/coverage2sql/