A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://github.com/nunit/nunit-console/issues/1578 below:

Isolate agents from the engine itself · Issue #1578 · nunit/nunit-console · GitHub

This is a long-standing direction for V4, but one for which no actual issue had previously been written. This issue aims to capture the overall goal and steps needed beyond what has been done to date.

Isolation of the various agents that run tests from the engine itself is an important feature because it allows the two sides to evolve separately. Perhaps more important, it will allow the agents to stop evolving when the runtimes they support reach EOL, while still allowing users to continue to use those agents if they need to.

Currently, agents do not reference the engine but they do reference engine.core, which is also referenced by the engine itself. We aim to eliminate nunit.engine.core. Types referenced by the engine will move into nunit.engine while those referenced by agents will move into a new assembly, nunit.agent.core. FWIW, I managed to do this with the TestCentric engine, only needing to duplicate a few types in the two surviving assemblies.

This issue has a soft dependency on #1049. It will be more convenient to first remove ExtensionManager and related classes from nunit.engine.core rather than moving those types twice.

Issue #909 has a similar soft dependency on this one.

issue #1539 is also related in that I would expect to create the new nunit.agent.core assembly as nullable in the first place.


RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4