The new version is just released (1.2.0 ) and now has an extra option: build_before_test. If you have a (for example) xamarin-archive step before nunit-runner , and you set the new build_before_test option to false, then test projects won’t be built twice.
At the same time, the following issue is solved by the new version:
opened 09:27PM - 10 Nov 16 UTC
closed 12:40PM - 06 Mar 17 UTC
Hi guys,
I've noticed that the NUnit-Runner step is always rebuilding the code … inside the step. This causes all my code to effectively build twice. I'd prefer to run the unit tests against already built nunit projects output by the Builder step.
Is it possible to make this step more compose-able with other steps such that, you are required to have a Builder step beforehand for it to work? For example the publish to Hockey step does not build the code inside its step, it requires the artefacts to already be built.
This would also reduce the maintenance work on this step to keep it in sync with changes to the Builder step.
Or at least can there be an option to build again if others are requiring this.
Thanks guys
Hi guys,
I’ve noticed that the NUnit-Runner step is always rebuilding the code inside the step for my Xamarin build. This causes all my code to effectively build twice. I’d prefer to run the unit tests against already built nunit projects output by the Builder step.
Can there be an option you select if the binaries are already built and should be compatible with NUnit?
Cheers
Happy Coding!
1 Like
