Add more integration tests (expect scripts) #1160
Closed
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
|
For some reason, those tests fails when using the brand new automated "npm install", so expect script are written to answer "No" to the last question, and bash script runs the commands manually. |
Toilal
force-pushed
the
integration-tests
branch
4 times, most recently
from
788b0cc to
17d825a
Compare
Toilal
force-pushed
the
integration-tests
branch
from
17d825a to
38f0200
Compare
|
Hey, I have been working on improving the CI tests for some time, and took a very different approach - one that doesn't rely on bash so windows users can run them too. Please have a look at #1218 |
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.
This adds more integration tests with expect scripts and some bash scripts.
I run this kind of tests on my fork since months and it does the job. I'm using TravisCI on my fork, but it should work with CircleCI too.
This check for many answers series (defined in expect scripts) if generation, lint, tests and build returns
0exit code.