All the integration testing has been moved to Bionic now and py3.5 is not tested runtime for Train or stable/stein. As per below ML thread, we are good to drop the py35 testing now: http://lists.openstack.org/pipermail/openstack-discuss/2019-April/005097.html  http://lists.openstack.org/pipermail/openstack-discuss/2019-April/004647.html  https://governance.openstack.org/tc/reference/runtimes/stein.html https://governance.openstack.org/tc/reference/runtimes/train.html Change-Id: Ib3ad13631f24983ac13531bb47f90897732bec60
Team and repository tags
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: https://docs.openstack.org/coverage2sql/latest/
- Source: https://git.openstack.org/cgit/openstack/coverage2sql
- Bugs: https://bugs.launchpad.net/coverage2sql
- Release notes: https://docs.openstack.org/releasenotes/coverage2sql
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
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/