test: add the e2e test leverage on docker-compose #626
Conversation
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
LinuxSuRen
force-pushed
the
e2e
branch
4 times, most recently
from
8d81f35 to
6159317
Compare
Author
|
Any news? Please let me know if there are anyting block it. |
Member
|
Thanks for the PR. There are many suites for e2e testing, and we can't give immediate feedback at this time. |
Author
|
Any news? |
Author
|
Finally, this PR was closed without any reasons. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
As mentioned in the title. This PR created the initial status of the e2e testing.
I'm not sure if maintainers think it's necessary to having the e2e testing. The importance of e2e testing is obvious, I'm not going to explain it here. But I'd be happy to make it be better if there are enough people willing to push it forward.
close #378