v0.1.14

What's Changed

• Qt -> 6.11.0 for QMLDom by @SanderVocke in #59

Full Changelog: v0.1.13...v0.1.14

qmldom (Qt v6.11.0)

Standalone (statically linked) qmldom binaries compiled from Qt 6.11.0.

Note that although this release is linked to a tag, the binaries are not necessarily built on that tag. It is just a necessity for Github releases. Please ignore the included source archives for this reason.

This "release" is also not necessary to use qoverage - it will be bundled in qoverage releases.

v0.1.13

What's Changed

• Update README.md by @SanderVocke in #57

Full Changelog: v0.1.12...v0.1.13

v0.1.12

What's Changed

• Change from .js companion files to collection singleton by @SanderVocke in #55

Full Changelog: v0.1.11...v0.1.12

Release v0.1.11 (pre-release)

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)
• 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.
• 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: v0.1.10...v0.1.11

Release v0.1.10 (pre-release)

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)
• 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.
• 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: v0.1.9...v0.1.10

Release v0.1.9 (pre-release)

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)
• 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.
• 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: v0.1.8...v0.1.9

v0.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 #52

Full Changelog: 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)
• 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.
• 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.

Qoverage v0.1.7 (pre-release)

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

• Fix pypi by @SanderVocke in #49
• Fixpypi by @SanderVocke in #50

Full Changelog: v0.1.6...v0.1.7

Known issues

• .js and .mjs files are not instrumented because they can not (yet) be parsed using qmldom (see 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.
• 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.

Qoverage v0.1.6 (pre-release)

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

• Update pyproject.toml to v0.1.6 by @SanderVocke in #44
• Move to qmldom built on manylinux for wider compatibility
• Some efforts to prepare reaching a WebAssembly build of qmldom, which are not yet included in the release (and may never)

Full Changelog: v0.1.5...v0.1.6

Known issues

• .js and .mjs files are not instrumented because they can not (yet) be parsed using qmldom (see 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.
• 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.