Hi, this is happening because the specs are run in a separate AppDomain and the output is not being copied back to the primary domain. It doesn't look too difficult to sort however I spend almost zero time in the .NET space these days, both this issue and #11 will have to wait till I get a gap not taken up by other projects. Its complicated by the fact that mspec made significant changes in splitting out their matchers after the version currently used in this project so any change brings in a whole host of testing and work not associated with the actual change. Ideally I need to find someone to take over this project that is more actively involved in the .NET space.
derekgreer
commented
4 years ago
Migrated from the vstest adapter repo
When running the following spec:
The output doesn't show up in the text explorer result pane as shown in http://stackoverflow.com/a/25785531 .
I'm using VS2013 if that matters.
Cheers.
Hi, this is happening because the specs are run in a separate AppDomain and the output is not being copied back to the primary domain. It doesn't look too difficult to sort however I spend almost zero time in the .NET space these days, both this issue and #11 will have to wait till I get a gap not taken up by other projects. Its complicated by the fact that mspec made significant changes in splitting out their matchers after the version currently used in this project so any change brings in a whole host of testing and work not associated with the actual change. Ideally I need to find someone to take over this project that is more actively involved in the .NET space.