Closed BrainCrumbz closed 8 years ago
This happened while another adapter (NSpec Test Adapter) was also installed in VS2015. After uninstalling that and opening the same sample solution, tests are shown in Test Explorer window. It seems this issue can be closed for now.
May be worth exploring a discovery strategy where only method level contexts are includes (methods defined on a class) and not going any deeper than that.
The discovery should enlist all found examples (in terms of NSpec domain), that are mapped to "runnable" test cases. What happens if one just stops at method level contexts? Maybe those have few or no examples at all defined, so in that case you'd see just a small part (or none) of available test cases.
True, but I've found I rarely run a single example. It's usually an entire context that I run. And I've found that deep nesting eventually evolves to class or method level contexts anyways.
Just something to consider (you can then just do static analysis of class structures).
Tried with SampleSpec solution. This is the output window log with trace min log level: