Closed ammaraskar closed 1 year ago
Looks good to me, I imagine we can replace it eventually without that much trouble as I'd like to go through with abstracting the Unity-specific code as much as possible.
Yeah, the nice thing is unity just uses nunit so it's pretty easy to move off it and just use nunit from a visual studio solution directly in the future.
As per the unity guide, this requires creating an assembly that depends on the
nunit.framework.dll
reference. In order to allow this testing assembly to access the code under the OpenTS2 folder, we create aScriptsAssembly
assembly that theTests
assembly can depend on.Unfortunately these tests can only be run through unity or the Rider IDE but unless we want to do a clean separation of all the Unity bits from the C# code this will likely be the easiest option.
If this looks good and we want to go with this for testing, I'll go ahead and add a github workflow so these tests run on CI.
Tests running in Unity
Tests in the Rider IDE