-
Notifications
You must be signed in to change notification settings - Fork 20
Use xunit2 for test discovery in-editor #88
Comments
Probably worth resurrecting the |
Looking forward to this! If you need someone to test this out let me know. |
Hi Matt. For a long time i've planned on doing some work on a spec / bdd kind of test tool. I'd like to take advantage of xunit2-discovery mechanisms so that i don't have to implement my own runner, especially r# support, since i guess this must be quite a lot of (recurring) work. |
Hi Matt, I currently have a custom Integration Fact (inherits from Fact) with its own Test Case Discoverer. I use an environment variable in the Discoverer to decide if the tests should be included (generally disabled to keep developers using the nimble unit tests locally). This approach works fine with VS - and the tests appear/ disappear based on the environment variable. Is that because of this issue? The tests are being discovered due to inheriting from FactAttribute? Code for that can be found here -> https://github.com/Red-Folder/RedFolder.xUnit.IntegrationFact |
@Red-Folder I believe it seems this is not longer being supported anymore, instead, R# supports xunit out of the box, and there's a corresponding bug-entry for this: https://youtrack.jetbrains.com/issue/RSRP-458779#tab=Comments Sadly enough nothing has changed. On the right hand side you can vote for this issue. |
@BrunoJuchli Does this plugin load in R# 2017.x? Because if JetBrains aren't going to implement custom test discovery, someone should. |
@tullo-x86 |
Currently, the in-editor test discovery uses the xunit1 API, rather than the xunit2 API that allows for custom test discovery. To use the xunit2 API to discover tests:
The text was updated successfully, but these errors were encountered: