It seems that either no unit tests are being discovered or they're not being run. This was working and there have been no configuration changes to my project settings, but when I checked in some new code changes none of the unit tests were discovered or run.
Unit tests not being discovered
Comments are currently closed for this discussion. You can start a new one.
Keyboard shortcuts
Generic
| ? | Show this help |
|---|---|
| ESC | Blurs the current field |
Comment Form
| r | Focus the comment reply box |
|---|---|
| ^ + ↩ | Submit the comment |
You can use Command ⌘ instead of Control ^ on Mac
#1 Posted by Feodor Fitsner Support staff on 16 Jun, 2014 04:27 AM
What testing framework is that?
#2 Posted by Feodor Fitsner Support staff on 16 Jun, 2014 04:45 AM
Also, do you have assemblies configured on Tests tab of project settings?
#3 Posted by Scott Dorman on 16 Jun, 2014 05:01 AM
All of the unit tests are built using MS Test. If you look at the history for build 1.0.23, you'll see that the unit tests were previously being discovered and run. I do have assemblies configured, using the following wildcard:
\.UnitTests.dll
I'm pretty sure this wildcard was also in place for the previous builds, when unit tests were discovered.
#4 Posted by Feodor Fitsner Support staff on 16 Jun, 2014 05:17 AM
There were some changes in wildcards matching (fixed recursive behaviour). If you are matching UnitTests.dll recursively in all folders use just
UnitTests.dll.#5 Posted by Scott Dorman on 16 Jun, 2014 05:24 AM
Yes, I'm matching recursively, but it should be finding any assemblies ending in .UnitTests.dll. Wouldn't I still need some sort of wildcard?
#6 Posted by Feodor Fitsner Support staff on 16 Jun, 2014 05:28 AM
Yeah, to match recursively any assembly ending with
.UnitTests.dlluse**\*.UnitTests.dll#7 Posted by Scott Dorman on 17 Jun, 2014 04:20 AM
That worked. Thanks!
Scott Dorman closed this discussion on 17 Jun, 2014 04:20 AM.