Qoverage

Latest version: v0.1.13

Safety actively analyzes 682471 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 1 of 3

0.1.13

What's Changed
* Update README.md by SanderVocke in https://github.com/SanderVocke/qoverage/pull/57


**Full Changelog**: https://github.com/SanderVocke/qoverage/compare/v0.1.12...v0.1.13

0.1.12

What's Changed
* Change from .js companion files to collection singleton by SanderVocke in https://github.com/SanderVocke/qoverage/pull/55

**Full Changelog**: https://github.com/SanderVocke/qoverage/compare/v0.1.11...v0.1.12

0.1.11

Pre-release so that there is a .whl available for other projects to work with.

As long as Qoverage is in the pre-release phase there will be no guarantees about stability w.r.t. semantic versioning.

Qoverage is bundled with qmldom built from Qt v6.6.1 and won't interfere with, or depend on your Qt installation.

Known issues

* .js and .mjs files are not instrumented because they can not (yet) be parsed using `qmldom` (see [QTBUG-116648](https://bugreports.qt.io/browse/QTBUG-116648))
* `qmldom` still sometimes fails to parse certain qml files due to various small issues. Such files will be treated as "coverable with zero coverage". In such cases, bug reports are submitted to the [Qt bug tracker](https://bugreports.qt.io).
* Running with the interactive collection mode (`qoverage collect -- some_command`) is untested.
* Python package is cross-platform but only bundles a `qmldom` tool for linux x64. On other platforms, `qmldom` (preferably 6.5.2) should be provided and specified with the QMLDOM env var.
* Plenty of Javascript constructs are not yet supported. Usually this leads to small parts of code not being included in the coverage analysis.
* The qmldom is built on manylinux, but the Python wheel itself is still not built on a forward-compatible abi3 setup. So the compatibility of the wheel may be limited.

**Full Changelog**: https://github.com/SanderVocke/qoverage/compare/v0.1.10...v0.1.11

0.1.10

Pre-release so that there is a .whl available for other projects to work with.

As long as Qoverage is in the pre-release phase there will be no guarantees about stability w.r.t. semantic versioning.

Qoverage is bundled with qmldom built from Qt v6.5.3 and won't interfere with, or depend on your Qt installation.

Known issues

* .js and .mjs files are not instrumented because they can not (yet) be parsed using `qmldom` (see [QTBUG-116648](https://bugreports.qt.io/browse/QTBUG-116648))
* `qmldom` still sometimes fails to parse certain qml files due to various small issues. Such files will be treated as "coverable with zero coverage". In such cases, bug reports are submitted to the [Qt bug tracker](https://bugreports.qt.io).
* Running with the interactive collection mode (`qoverage collect -- some_command`) is untested.
* Python package is cross-platform but only bundles a `qmldom` tool for linux x64. On other platforms, `qmldom` (preferably 6.5.2) should be provided and specified with the QMLDOM env var.
* Plenty of Javascript constructs are not yet supported. Usually this leads to small parts of code not being included in the coverage analysis.
* The qmldom is built on manylinux, but the Python wheel itself is still not built on a forward-compatible abi3 setup. So the compatibility of the wheel may be limited.

**Full Changelog**: https://github.com/SanderVocke/qoverage/compare/v0.1.9...v0.1.10

0.1.9

Pre-release so that there is a .whl available for other projects to work with.

As long as Qoverage is in the pre-release phase there will be no guarantees about stability w.r.t. semantic versioning.

Qoverage is bundled with qmldom built from Qt v6.5.3 and won't interfere with, or depend on your Qt installation.

Known issues

* .js and .mjs files are not instrumented because they can not (yet) be parsed using `qmldom` (see [QTBUG-116648](https://bugreports.qt.io/browse/QTBUG-116648))
* `qmldom` still sometimes fails to parse certain qml files due to various small issues. Such files will be treated as "coverable with zero coverage". In such cases, bug reports are submitted to the [Qt bug tracker](https://bugreports.qt.io).
* Running with the interactive collection mode (`qoverage collect -- some_command`) is untested.
* Python package is cross-platform but only bundles a `qmldom` tool for linux x64. On other platforms, `qmldom` (preferably 6.5.2) should be provided and specified with the QMLDOM env var.
* Plenty of Javascript constructs are not yet supported. Usually this leads to small parts of code not being included in the coverage analysis.
* The qmldom is built on manylinux, but the Python wheel itself is still not built on a forward-compatible abi3 setup. So the compatibility of the wheel may be limited.

**Full Changelog**: https://github.com/SanderVocke/qoverage/compare/v0.1.8...v0.1.9

0.1.8

Pre-release so that there is a .whl available for other projects to work with.

As long as Qoverage is in the pre-release phase there will be no guarantees about stability w.r.t. semantic versioning.

Qoverage is bundled with qmldom built from Qt v6.5.3 and won't interfere with, or depend on your Qt installation.

What's Changed
* Add AST to intermediate outputs by SanderVocke in https://github.com/SanderVocke/qoverage/pull/52

**Full Changelog**: https://github.com/SanderVocke/qoverage/compare/v0.1.7...v0.1.8

Known issues

* .js and .mjs files are not instrumented because they can not (yet) be parsed using `qmldom` (see [QTBUG-116648](https://bugreports.qt.io/browse/QTBUG-116648))
* `qmldom` still sometimes fails to parse certain qml files due to various small issues. Such files will be treated as "coverable with zero coverage". In such cases, bug reports are submitted to the [Qt bug tracker](https://bugreports.qt.io).
* Running with the interactive collection mode (`qoverage collect -- some_command`) is untested.
* Python package is cross-platform but only bundles a `qmldom` tool for linux x64. On other platforms, `qmldom` (preferably 6.5.2) should be provided and specified with the QMLDOM env var.
* Plenty of Javascript constructs are not yet supported. Usually this leads to small parts of code not being included in the coverage analysis.
* The qmldom is built on manylinux, but the Python wheel itself is still not built on a forward-compatible abi3 setup. So the compatibility of the wheel may be limited.

Page 1 of 3

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.