Skip to content

Chrome tests fail with multiple frameworks with parallelExecution in Test := true #47

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.

Sign up for GitHub

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

Jump to bottom
Open
nicolasstucki opened this issue Apr 18, 2016 · 3 comments
Open

Chrome tests fail with multiple frameworks with parallelExecution in Test := true #47

nicolasstucki opened this issue Apr 18, 2016 · 3 comments
Labels
bug

Comments

@nicolasstucki
Copy link
Contributor

The issue is with the Scala.js test interface. It seems that on Chrome, the first framework (JUnit, ScalaTest or uTest) to run succeeds and then the following frameworks fail when trying to cast their test suite classes.
As far as I saw, if tests are executed in only one framework the tests succeed.
@nicolasstucki nicolasstucki mentioned this issue Apr 18, 2016
Closed
@nicolasstucki
Copy link
Contributor Author

The frameworkDetector.js is returning correctly the framework in Firefox and Chrome.

@nicolasstucki
Copy link
Contributor Author

If all tests pass if they are executed with parallelExecution in Test := false.

@nicolasstucki
Copy link
Contributor Author

If I have 3 test frameworks, then sbt is opening 3 instances of Chrome with testFrameworkInfo.js, 3 with testMaster.js and the slaves.
@gzm0 is this how it is supposed to work? If it is, do you have some insight that might help me finding the source of this bug.

@nicolasstucki nicolasstucki changed the title Chrome tests fail with multiple frameworks. Chrome tests fail with multiple frameworks with parallelExecution in Test := true May 12, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@nicolasstucki