Repository navigation
P23: features=coverage (coverage after Tests) - #24
Merged
Merged
Conversation
"coverage" in features= switches on glpython-editor's coverage after Tests: when all examples pass, the report lists the lines of the block's functions that no example executed, or a neutral note that every line ran (which doesn't show whether the examples check the edge cases). It is the one name that a block without features= doesn't get, so existing profiles and blocks stay as they are. README documents it (with a rezept3 profile as example); examples/profiles.md has a rezept3 slide with the reference cases, a library as second file, a failing example and the same block with rezept. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
P23. Depends on glpython-editor#39 (the embed's
coverage). Merge after that PR is merged and Pages has deployed.Merging this one first does no harm: an older embed ignores the unknown
coveragein?features=, and no course lists it yet. The README would just describe something that doesn't happen yet.Changes
coverageis a known name infeatures=, so it no longer triggers the «Unbekannt in features=» warning, and it is passed on to the embed.features=doesn't get. Theerkunden,rezept,pruefungprofiles and blocks without options stay unchanged.coverageshows and its limit (untested code, not wrong code). Nothing is marked in LiaScript's editor; the report gives the line and its code. Profile example@Code.rezept3.examples/profiles.md: arezept3slide with:noten.py)rezeptTested in LiaScript
rezept3slide, «Tests» on each block:ist_genuegendbewertungvorzeichenschnitt+noten.pynoten.py)bewertungbewertungwithrezeptcheck-macropasses.🤖 Generated with Claude Code