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

Feature request: forkMode always #99

Open
pan3793 opened this issue Oct 2, 2022 · 4 comments
Open

Feature request: forkMode always #99

pan3793 opened this issue Oct 2, 2022 · 4 comments

Comments

@pan3793
Copy link

pan3793 commented Oct 2, 2022

it's useful for integration tests that contain lots of singletons, because it's hard to pick up all singletons and reset them if we want to change the configuration(which will affect those singleton objects) in another test.

@cheeseng
Copy link
Contributor

cheeseng commented Oct 3, 2022

@pan3793 Makes sense, imho we may want to support this in org.scalatest.tools.Runner, e.g. to have a server running in the main process which forks child process that use socket reporter to send back the result back to the reporters on the main process. We have similar thing in the sbt's Framework class that's called by sbt, we can probably do similar thing in ScalaTest own Runner.

@bvenners What do think about the idea?

@pan3793
Copy link
Author

pan3793 commented Oct 24, 2022

Hi @cheeseng, is there a plan and ETA to support it? currently, we must fall back to JUnit since the maven surefire plugin support it.

@cheeseng
Copy link
Contributor

@cheeseng Hmm, unfortunately I don't have a ETA for you, but I do want to get started on it, though I also struggle on what's the best next step for it.

@pan3793
Copy link
Author

pan3793 commented Oct 24, 2022

Anyway, thanks for your quick response and maintaining such a great tool.

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

No branches or pull requests

2 participants