@ztone thanks for this!

Just throwing this out there as an idea: how about we use the same code file for both RoslynScriptEngineTests and MonoScriptEngineTests?

We could name it ScriptEngineTests and link it into each project. For now we'd have to use #if to omit certain tests for mono, which is quite ugly, but at least it would allow us, at a glance, to see the difference in the unit tests for each of the two types.

There is of course a fundamental difference between the two which is the use of the RoslynScriptEngine/MonoScriptEngine and RoslynTestScriptEngine/MonoTestScriptEngine types but this could be done using one #if at the top

#if MONO
using ScriptEngine = RoslynScriptEngine;
using TestScriptEngine = RoslynTestScriptEngine;
#else
using ScriptEngine = MonoScriptEngine;
using TestScriptEngine = MonoTestScriptEngine;
#endif

@scriptcs/core thoughts?

@adamralph I somewhat expected this to be raised as the tests just have minor differences and are in strict sense dups. Having a shared tests project will insure that both engines support the same logic and keeps them in sync.

However, engines have minor differences, e.g. comments after evaluation is not as well supported in Mono as in Roslyn, logic around when IsCompleteSubmission is not the same for engines and probably some other stuff.

There are pros and cons with both approaches. I'm good either way ... just wanted the engine tested.

Great work. I agree with @adamralph 100% but I think priority 1 for now is to get any tests in - right now there is hardly any safety blanket around the Mono engine.
Let's think of reconciliation between the engine tests later on, as of now I'm going to pull this in. Thanks a lot @ztone

👍