Add unit test support and add unit test for new chroot_correct_qemu logic that is out of execute_chroot_script #245
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
guysoft
force-pushed
the
feature/unit-testing
branch
from
c2296ef to
15370fe
Compare
|
Looks like this works and there are tests now, merging |
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.
The code block in execute_chroot_script has been causing a lot of confusion to what needs to execute. I think its time to start adding unit tests and define what we want it to do.
This PR splits some of the logic in to common.sh and also adds methods to run unit tests, as well as automated ci for the unit test.
Related: #240