Conversation
This is kind of hacked together as "Test Sequence Example Test", the idea being this is an example of how a test sequence might be contructed for testing zar. Currently, the existing tests still exist, but the idea would be to replace them with this setup completely (allowing for the code to be majorly simplified). This will allow us to more easily test more features in the future.
moosichu
force-pushed
the
feature/improved-testing
branch
from
11bfa6b to
d027ad9
Compare
… also test stderr and stdout of archivers, start to implement memory ownership and fix test artifact production for debugging
…so that temporaries can be safely handed over
…m instead of hardcoding it in
… tests (needs work.. but is fine for now?)
Owner
Author
|
This has already been merged! |
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
1 participant
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.
Very WIP and will wait until #62 is closed before merging this (don't want to create headaches there). This would be to address #76. For now "Test Sequence Example Test" in this merge is the one to keep an eye on.