test: introduce new testing framework #46
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
longfangsong
force-pushed
the
new-test-framework
branch
2 times, most recently
from
210d1a5
to
4d0a7ab
Compare
longfangsong
force-pushed
the
new-test-framework
branch
from
4d0a7ab
to
debfd43
Compare
longfangsong
force-pushed
the
new-test-framework
branch
from
b56f62e
to
698b279
Compare
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.
What problem does this PR solve?
Issue Number: close #26
Problem Summary:
Currently, doing integration tests are so hard.
What is changed and how it works?
What's Changed:
Now just add the test cases into
test_cases, andmake integration_testwill do the job.Docker, Python and jinjia2 is required, hopefully these requirements can be made simpler (in a single docker) in the future.
How it Works:
TopTest.scalaandProgramRom.scalafor each test caseRelated changes
shuorv/doc/: (WIP)