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

v4: Create ITestPackage interface #950

Closed
wants to merge 2 commits into from
Closed

v4: Create ITestPackage interface #950

wants to merge 2 commits into from

Conversation

ChrisMaddock
Copy link
Member

Fixes #919. Addressing this first, as it's blocking #885.

This creates an ITestPackage interface, and moves the TestPackage class to nunit.engine.core.dll. In the longer term vision (#885) - I'd expect ITestPackage to be moving to the "extensions-core" API assembly, which is the primary motivation to bring in a minimal interface rather than keeping the class itself in that assembly.

This leaves us in the slightly ugly interim state where the only way for a runner to create a TestPackage is by first creating a TestEngine through TestEngineActivator. My thinking is that when (if) we address #948 that will be addressed, and we can re-expose the normal TestPackage constructors.

@ChrisMaddock ChrisMaddock reopened this May 9, 2021
@ChrisMaddock ChrisMaddock linked an issue May 9, 2021 that may be closed by this pull request
@ChrisMaddock
Copy link
Member Author

Closing this one. I still think this should be a part of v4, but it's more than I have time to tackle at the moment.

@CharliePoole CharliePoole deleted the issue-919a branch January 3, 2022 20:04
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.

Where should TestPackage be defined?
1 participant