CharliePoole
CharliePoole
Obviously, the current implementation is the following: - First, the Properties which are used for TestCaseSource are asked (static or not) - Then the methods attributed with TestFixtureSetUp are called....
NOTE: Only issues that require porting are listed. In some cases V3 issues pertain to features, which are being dropped. - [ ] #1570 (not sure... may have been done...
With the use of pluggable agents and the elimination of built-in agents, the `nunit-agent.core` assembly is no longer used in the .NET Framework builds of the engine, i..e. the so-called...
@nunit/engine-team I'm creating this issue to help us get rid of bugs in the V4 build. Let's use it as follows. 1. If you want to work on any of...
Currently, `ProcessRunner.RunAsync()` creates a task which calls the synchronous `Run` method in the agent. `TestAgentRunner.RunAsync`, which is used in the agents does the same thing in calling the driver. We...
We currently have to trigger the build manually after publication of the draft release on GitHub. It should run automatically.
We have a linux solution file but it has not been tested for some time. We should get it building and then add it to our workflow actions.
@nunit/engine-team Actually, I'm debating whether to do this and looking for input Reasons Pro... * We're developing V3 and V4 at the same time, so only one can use main...
Part of #1607 in #770, @ChrisMaddock proposed the following... > ## Engine API assembly > Funny one - I currently see the API assembly as serving two distinct purposes. >...
@nunit/engine-team @nunit/core-team We already have a number of individual issues around changing the engine's modular structure. I noticed that we don't have a single issue that incorporates an overview, so...