We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Recently had 75+ instances of Beyond Compare open as all the tests failed.
Beyond Compare and KDiff both support opening multiple files or directory comparison.
I'm not sure how I would implement this yet... but it would be nice if diffs are opened at the end of the test run.
The text was updated successfully, but these errors were encountered:
Two possible options.
AppDomain.Unload
Sorry, something went wrong.
@josephwoodward FWIW this is how it is handled in diffengine https://github.com/VerifyTests/DiffEngine/blob/master/docs/diff-tool.md#maxinstancestolaunch
DiffRunner.MaxInstancesToLaunch(5); helps solve the problem without having to mess about with AppDomain.Unload
DiffRunner.MaxInstancesToLaunch(5);
Happy to close.
🤦♂️ that was in another project.
yes, we should copy that approach or perhaps even better integrate with DiffEngine. i'm happy to pick this up and fix.
No branches or pull requests
Recently had 75+ instances of Beyond Compare open as all the tests failed.
Beyond Compare and KDiff both support opening multiple files or directory comparison.
I'm not sure how I would implement this yet... but it would be nice if diffs are opened at the end of the test run.
The text was updated successfully, but these errors were encountered: