Unit test build jobs fail silently
Currently the unit test jobs do not actually run any unit tests, but still reports success back to gitlab.
This is due to a change in !82 (merged) that moved to the PackageReference system instead of the packages.config system for managing nuget packages. Now we don't have Nunit.ConsoleRunner in the expected location.
We don't see this failure because of the powershell+gitlab caveat here: gitlab-org/gitlab-runner#3194. When we have fixed the unit test issue, we should probably set the
ErrorActionPreference variable to
stop globally in the script.