Include boost-ext/ut micro unit test library #139
Merged
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
jt-traub
commented
Oct 9, 2023
jt-traub
commented
Oct 9, 2023
jt-traub
commented
Oct 9, 2023
jt-traub
commented
Oct 9, 2023
jt-traub
commented
Oct 9, 2023
jt-traub
commented
Oct 9, 2023
jt-traub
commented
Oct 9, 2023
jt-traub
force-pushed
the
jt-add-boost-ut
branch
2 times, most recently
from
fcf3cc3 to
a814bac
Compare
jt-traub
commented
Oct 9, 2023
Begin process of wiring up creating and running unit test.
jt-traub
force-pushed
the
jt-add-boost-ut
branch
from
a814bac to
20e629c
Compare
valdisz
approved these changes
Oct 10, 2023
|
LGTM, I will push the merge button |
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.
This adds the Boost μt unit testing framework to the codebase.
This is a header-only freely redistributable framework which encapsulates most different unit testing styles (suites, rspec, gherkin). For the tests here, I am using the most simple 'suites' style, but we could use other styles as well.
The overall engine however, is not very amenable to unit testing in it's current state. I have provided some examples of testing various functions within the faction and unit classes, in order to provide some guidance on how tests might be written, but writing thorough tests will be hard without refactoring a lot of the current engine framework. That is something I believe should be undertaken over time however.