Skip to content

Enable Scala.js test #9973

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

Merged
merged 9 commits into from
Oct 9, 2020
Merged

Conversation

liufengyun
Copy link
Contributor

Enable Scala.js test

Copy link
Member

@sjrd sjrd left a comment

Choose a reason for hiding this comment

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

Thank you :)

liufengyun and others added 5 commits October 9, 2020 11:35
The process pool is only needed for run tests.
Co-authored-by: Sébastien Doeraene <[email protected]>
As mentioned in [1]:

> JUnit creates a new instance of the test class before invoking each
> @test method. This helps provide independence between test methods and
> avoids unintentional side effects in the test code. Because each test
> method runs on a new test class instance, we can’t reuse instance
> variable values across test methods.

Each `@Test` method would create a new instance of the test classes,
which means each `@Test` method would create N new processes.

[1]: https://stackoverflow.com/questions/14010222/junit-new-instance-before-invoking-each-test-method-what-are-the-benefits
@anatoliykmetyuk anatoliykmetyuk merged commit b22331e into scala:master Oct 9, 2020
@anatoliykmetyuk anatoliykmetyuk deleted the windows-ci branch October 9, 2020 14:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants