Create separate project for TestCentric.Engine.Api package

[CharliePoole]

The testcentric-engine GitHub project produces three different NuGet packages

• TestCentric.Engine
• TestCentric.Engine.Core
• TestCentric.Engine.Api

TestCentric.Engine depends on the other two and the Core package depends on the Api. In addition, some engine extensions depend on the Core and/or the Api assemblies. In particular, all pluggable agents depend on both.

Even though the references are not circular, this gives rise to a kind of functional circular dependency, which was first noticed in working on issue #127 and gave rise to an adhoc fix in our Cake recipe.

• TestCentric.Engine depends on Core and Api.
• Pluggable agents also depend on them.
• The build process for the engine creates all three packages simultaneously.
• The package testing process for the engine requires working pluggable agents.

One way to resolve this would be to build all our pluggable agents, or at least those distributed with the engine, as part of the testcentric-engine project. But this would leave us open to other future extensions possibly creating the same situation.

In any case, it seems simpler for each of our GitHub projects to only produce a single package. (In some cases there might be different formats delivered, such as NuGet and Chocolatey, but the functionality of the packages would be the same.)

This issue addresses separation of the TestCentric.Engine.Api package. The TestCentric.Engine.Core package will be addressed in a separate issue. Once these changes are complete, we will be able to simplify our Cake recipe accordingly.

[CharliePoole]

:tada: This issue has been resolved in version 2.0.0-beta3 :tada:

The release is available on:

• GitHub Release
• NuGet Package