Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: run jest script in jest dir #1245

Merged
merged 1 commit into from
Sep 26, 2019
Merged

chore: run jest script in jest dir #1245

merged 1 commit into from
Sep 26, 2019

Conversation

sangaman
Copy link
Collaborator

@sangaman sangaman commented Sep 24, 2019

This prevents the jest script from running any nested versions of xud such as those that may be installed in the simulation test temp dir.

It also separates the seedutil tests from running with the rest of the jest tests and removes its dependencies from the travis config.

@sangaman sangaman added automated tests build Related to build process and automation labels Sep 24, 2019
@sangaman sangaman requested a review from a user September 24, 2019 15:44
@sangaman sangaman self-assigned this Sep 24, 2019
Copy link
Contributor

@michael1011 michael1011 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

When having a look at why you removed npm run compile:seedutil, I noticed that we aren't running the seedutil tests at all on Travis (they are not included in npm run test and npm run test:sim). Is this intentional?

@sangaman
Copy link
Collaborator Author

Yeah it's intentional, I figured that the seedutil code is separate and mostly static such that we don't gain much from compiling and running it every build. Paricularly with the pending Raiden changes which makes the build take much longer.

@michael1011
Copy link
Contributor

@sangaman I wouldn't feel to comfortable not running some tests at all in the CI.

What about using a build matrix similar to what LND is doing? This would allow that the seedutil is compiled and tested in parallel to the normal CI script? (If we agree on setting it up it doesn't have to be implemented in this PR though)

@sangaman
Copy link
Collaborator Author

Hmm ok I will put it back in for now, I think longer term it's worth changing though. I'll look into a build matrix or another approach to split it off from our main suite of tests.

@sangaman sangaman force-pushed the test/jest-script branch 2 times, most recently from 40a94b4 to cb1c1c7 Compare September 25, 2019 17:34
This prevents the jest script from running any nested versions of xud
such as those that may be installed in the simulation test temp dir.

It also separates the seedutil tests from running with the rest of the
jest tests.
@michael1011 michael1011 merged commit 1b642fb into master Sep 26, 2019
@michael1011 michael1011 deleted the test/jest-script branch September 26, 2019 16:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
automated tests build Related to build process and automation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants