feat: core test output parsing #82
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
fredrikaverpil
force-pushed
the
feat/test-status-by-output-filtering
branch
3 times, most recently
from
8480509 to
111ad72
Compare
fredrikaverpil
force-pushed
the
feat/test-status-by-output-filtering
branch
from
92b4bb4 to
f0d71cc
Compare
fredrikaverpil
changed the title
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.
Here I'm playing around with leveraging the work previously done for the "dir" position type's test result parsing, but for the "test" position type. It might actually be possible to run tests through a main "core" logic which is shared across strategies... 🤔
Aims to fix #4 but might also have some awesome, positive, side-effects.
Needs cleaning up and refactoring, but I'll be running this setup for a few days to see how it performs... 🤞