Test all functionality #69
Draft
Conversation
This file contains 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
We now introduce `tests.mk` in the intro chapter. However, the tests will be covered in each chapter (i.e. in the NOWEB file of each include). There is a `tests.nw` file which sets up the structure. This file is covered in the introduction. However, each file, e.g. `tex.mk.nw`, will also have a code block `<<tests.mk>>` containing all test code. Then `tests.mk` can be constructed from `tests.nw tex.mk.nw` and so on. The rationale is that the tests should be with the code. Otherwise they risk getting out of sync.
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.
Write tests for all functionality. These tests can be included as examples in the documentation.