-
-
Notifications
You must be signed in to change notification settings - Fork 731
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Get return code from intercepted process in SpecFlow TestExecutionReport #1160
Comments
@gep13 @patriksvensson @devlead if ok, You may assign this to me. |
@mholo65 Done! |
@patriksvensson 👍 This probably means that I may implement this feature 😄 |
@mholo65 Yes! 😄 |
@mholo65 any progress made in this area? |
@devlead actually, I have implemented this already (or think I have, might be only stored locally on one of my computer).. Just need to find it, rebase and fix a test before committing a PR. Somehow I have forgot about this 😄 What's the timeframe for 0.17.0? |
@mholo65 Depending on available time 😄 , feature freeze is planned for this weekend. |
@devlead ok, I'll see if I could dig it up til then! |
@mholo65 Perfect 👌 |
@mholo65 thanks again for this contribution! |
In order to know if tests passed/or failed, then SpecFlow TestExecutionReporter should return the code of the intercepted process (Unit test runner).
Another alternative would be to create an alias which takes the results of the Unit Test runner and converts it to a report using SpecFlow (this is how SpecFlow is designed to work).
The text was updated successfully, but these errors were encountered: