vprusso/toqito

toqito/state_props/is_separable.py is the least-covered module in the project, at about 88% with roughly 32 uncovered lines. Everything else is at or near 100%, and the repository overall sits just under 99%. This module matters more than the number suggests: it dispatches across a series of separability criteria, and the uncovered lines are mostly individual criteria branches that never get exercised. A bug in one of those branches would return a wrong separability verdict rather than raising, which is the kind of failure that is easy to miss. What to do Find the uncovered lines and add tests that reach them: uv run pytest --cov-config=.coveragerc --cov=toqito --cov-report=term-missing \ toqito/state_props/tests/test_is_separable.py Use the Missing column to see which lines are unreached. Note the --cov=toqito part: running coverage against a single submodule triggers a numpy "cannot load module more than once" error, so keep it as written. Then, for each uncovered branch, construc

The documentation build executes the Examples code blocks in docstrings (the ```python exec="1" blocks), so a runnable example doubles as documentation and a lightweight smoke test. Several public functions have no Examples section. What to do Add an Examples section with a short, runnable snippet, matching the existing style: ```python exec="1" source="above" result="text" import numpy as np from toqito.states import dicke print(dicke(...)) ``` Good targets (pick one or a few per PR): toqito/measurement_ops/measure.py toqito/states/dicke.py toqito/state_props/has_symmetric_inner_extension.py toqito/state_props/integral_relative_entropy.py the cone builders in toqito/cones/ (e.g. geometric_mean_epi_cone.py) Verifying The example runs during the docs build: uv sync --group docs cd docs && uv run mkdocs build Confirm the snippet runs without error and the printed output is sensible. Looking at an existing function's Examples section (e.g. toqito/channels/dephasing.py) is the easiest