You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 7, 2019. It is now read-only.
As per my comment on a previous issue, it would be good to get the Produce output on builds info added to the readme. In addition, I think the follow two tips would be great:
To automate testing of your specs:
In project.json, add a dependency to xunit.runner.dnx (at time of writing, version 2.1.0-rc1-build204).
Add a second command (in addition to the one used by the prebuild element) as follows:
"test": "xunit.runner.dnx"
This will make your specs appear in test explorer.
Okay, I saw your other comment first, and have updated the README for "produce outputs".
Good idea for the tips. Did you want to submit a PR (then you'll get the credit)? If so, I suggest referencing the sample project.json, in particular not including the dependencies as framework dependencies (otherwise each framework has to independently reference).
As per my comment on a previous issue, it would be good to get the
Produce output on builds
info added to the readme. In addition, I think the follow two tips would be great:To automate testing of your specs:
project.json
, add a dependency toxunit.runner.dnx
(at time of writing, version2.1.0-rc1-build204
).prebuild
element) as follows:"test": "xunit.runner.dnx"
This will make your specs appear in test explorer.
The overall output will be along the lines of:
The above is obvious if you've ever done work with DNX in the past, but for people entering the arena it would be helpful I'm sure.
The text was updated successfully, but these errors were encountered: