Multicomputer/Multiplatform testing environment

I have been supporting the use of NUnit in a two computer testing environment for years now.

That environment has been a Windows/.NET 4.7 PC Host, and a Windows CE/Compact Framework 3.5 Test machine, connected by SSH and SFTP.

I run a GUI on the Host side, and NUnitLite on the test machine.

I currently support about 99% of the full NUnit 3.13.2 testing framework in that environment,

My context is now changing. I now need to run a Windows/.NET Core PC Host machine, and a Linux/Mono/.NET 4.6 Test machine.

Since I now have access to the full Linux/Mono environment, I would like to be able to run a more normal set of testing pieces. My preference would be a NUnit Console or TestCentric GUI on the Host machine, and normal test assemblies (not NUnitLite) on the Test machine.

It is unclear to me from all of the discussions on both this and the TestCentric repo how close to being able to do this things are.

I am currently using the exact same testing environment/communication protocols as I was previously on the Host machine, and using unmodified mono NUnitLite on the Test machine, controlling the testing through the command line on the test machine as was previously the case. This works, but limits things to the way they have always been. None of the capabilities of the engine/agent, or the new GUI, are available, and all test assemblies must be compiled with NUnitLite.

Where are things in regards to allowing the full environment I would like to make available working? This seems to need a full TCP based engine/agent communications protocol, and a fully supported cross platform (Windows & Linux/Mono) capability.

Since this is the environment I work in daily, I would like to be able to contribute to whatever work still needs to be done to make this possible.

I hope that @CharliePoole and @ChrisMaddock will be able to provide insight into this.

Start by reviewing the existing NUnit Console, NUnitLite, engine/agent, and SSH/SFTP communication setup described in the issue. The goal is to determine what remains for a TCP-based engine/agent protocol supporting a Windows/.NET Core host and Linux/Mono test machine with normal test assemblies.