2024-11-28 21:18:10 -08:00
2024-11-27 21:12:30 -08:00
2021-05-31 15:06:33 -05:00
2019-04-17 15:47:06 +09:00
2022-06-16 14:45:04 +00:00
2020-08-02 19:33:34 +00:00
2016-11-11 19:40:27 +09:00
2019-04-17 15:40:38 +09:00
2019-04-19 19:36:21 +00:00
2016-04-19 12:24:29 +09:00
2017-12-16 17:45:42 +09:00
2024-11-28 21:18:10 -08:00
2016-04-19 12:24:29 +09:00
2024-11-28 21:18:10 -08:00
2020-04-19 17:56:05 -05:00
2018-09-12 16:49:35 -06:00
2016-04-19 12:24:29 +09:00
2016-11-11 11:33:43 +09:00
2019-04-23 17:16:38 +08:00
2017-04-27 16:53:43 +09:00
2024-11-28 21:18:10 -08:00
2020-04-17 17:08:58 +02:00
2021-01-02 10:25:29 +08:00
2023-01-19 11:20:12 +01:00
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: https://docs.openstack.org/coverage2sql/latest/
- Source: https://opendev.org/openstack/coverage2sql
- Bugs: https://bugs.launchpad.net/coverage2sql
- Release notes: https://docs.openstack.org/releasenotes/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 headThis 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 .coverageThere are several options for running coverage2sql, they can be listed with:
coverage2sql --helpThe 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/