Repository navigation
test: prove the ledger, the coverage matrix, the refusal text and the validation rules of models and programs - #128
Merged
Merged
Conversation
… validation rules of models and programs
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.
A test keeps the ledger honest: a
donerow ofFEATURES.mdnames a test that exists (documents and workflows count only for rows whose proof is a file), and a link that leads nowhere fails; 39 rows got their test links. The coverage matrix is held to the same rule for every row, not only for the rows that the code declares: a faithful mark of a release that is out links to a test, and no link leads nowhere (one mark of release 0.2 had none). Gaps that coverage showed are closed: the default methods of theBackendtrait refuse, name the backend and the action (three of them said "this" for the backend, now fixed), the text of a refusal is checked (line, mark, feature, backend, reason, fix; also for a value from a parameter), and the rules of periodic, Markov and trace models and the limits and waits of a program of your own are each violated once and refused with their place.To know: the marks of the next release stay plans until the release pull request raises the version of the crates; from then on they need their links. The only change outside tests is the name of the backend in three default refusals. No change to the format, the API or the dependencies.