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

Support multiple installed engines #1132

Closed
CharliePoole opened this issue Dec 12, 2015 · 2 comments
Closed

Support multiple installed engines #1132

CharliePoole opened this issue Dec 12, 2015 · 2 comments

Comments

@CharliePoole
Copy link
Contributor

This may end up being a non-issue, if our existing code takes care of the job, but I have a suspicion it doesn't. Here's what we need to verify and/or implement:

  • Multiple engines can be present in well-known locations or pointed to from the registry or settings.
  • All such engines should be examined by the EngineActivator when deciding which engine to use.
  • Each engine may potentially have it's own set of extensions.
  • Each engine may also point to a set of shared extensions.
  • In addition to such "findable" engines, any runner may be packaged with a private engine. Such an engine will not be available to other runners.
  • The engine that is found and used by a runner should be easily identifiable by the user, in order to facilitate bug reporting and debugging.

While this is not a user-facing feature, being able do the above is a prerequisite for other features we want to implement.

@CharliePoole CharliePoole added this to the 3.2 milestone Dec 12, 2015
@CharliePoole CharliePoole self-assigned this Dec 28, 2015
@CharliePoole CharliePoole modified the milestones: 3.4, 3.2 Feb 20, 2016
@CharliePoole
Copy link
Contributor Author

Postponing this... it's important but not urgent.

@CharliePoole
Copy link
Contributor Author

Issue moved to nunit/nunit-console #3 via ZenHub

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants