Repository navigation
Write up recommended way to test and link it from the readme #2973
Description
Activity
Thanks for taking the time to write up the readme!
The reason I was asking in the first time is because I looked at the contribution guide and it didn't mention it. I did a search on the repo for "run tests" "running tests" and couldn't find anything. I found the build script (it's in the root directory....) but couldn't figure out whether I could use it to run tests. Also I didn't think to look at the build-script page because.. you know I found the script already. My mistake.
Also I can't seem to get the test to run with Resharper. So, mainly because I was too lazy, I just thought I'd create the pull requests and have the CI servers run the tests for me (although I would have preferred to run them myself before publishing the PR and causing anyone to invest time into reviewing an incomplete PR).Since you mention Resharper: I've tried running the tests with R# (2018.2 EAP 7 or 8, VS 2017.7) but they all end up with "Inconclusive". Starting with debugging there's an exception stating that Nunit 3.11 is not supported.
I've tried manually configuring the path to Nunit @ Resharper settings. I've chosen bin/Debug/net4.5 (and tried /Release, too) of the checked-out and built repository. Resharper finds nunit but the tests are still inconclusive.
What do I need to do to get the tests running @r#?- added 2 commits that reference this issue
on Aug 23, 2018 Hi @BrunoJuchli
A multi-year follow up I know, but I wondered if you had any joy getting the Rider test runner working such that you could run tests directly in the IDE?
It seems that JetBrains have had a bit of trouble circa 2018 / 2019 with their auto-detection of tests, see: https://twitter.com/jetbrainsrider/status/1123930158627299328
However, it's 2021, I'm using the latest Rider (2021.1.2) and the issue is still occurring for me.
@FrankRay78
Haven't tried again ever since. We're currently using xunit only in our projects, so...
On a sidenote: xunit 2.0 features are mostly still unsupported by R#/rider. There's been no significant development there for years.Reacted by Frank RayFYI - I'm going to take this issue @rprouse
Thanks @FrankRay78
FYI, I made a pass at getting the tests to run in Visual Studio recently but couldn't get them working. Now that @OsirisTerje has released the 4.0 version of the adapter, we might have more luck.
Hi Rob. I propose to address this issue with a more general documentation update to the BUILDING.md file, and then specifically address issue #3008 which covers running tests in the IDE. I hope this approach is acceptable.
Reacted by Rob ProuseUpdate. PR submitted to (hopefully) close this issue - #3875
I find https://github.com/nunit/nunit/blob/master/BUILDING.md#build-script a bit vague and we've had a number of folks asking us how we test.
I think there's a lot of room for personal style assuming we have solid CI. My ideal workflow:
.\build.ps1 -t testto make sure the passes and failures are as expected