Skip to content
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

Closed
bjorkstromm opened this issue Aug 16, 2016 · 10 comments
Closed
Assignees
Milestone

Comments

@bjorkstromm
Copy link
Member

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).

@bjorkstromm
Copy link
Member Author

@gep13 @patriksvensson @devlead if ok, You may assign this to me.

@patriksvensson
Copy link
Member

@mholo65 Done!

@bjorkstromm
Copy link
Member Author

@patriksvensson 👍 This probably means that I may implement this feature 😄

@patriksvensson
Copy link
Member

@mholo65 Yes! 😄

@devlead
Copy link
Member

devlead commented Oct 20, 2016

@mholo65 any progress made in this area?

@bjorkstromm
Copy link
Member Author

@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?

@devlead
Copy link
Member

devlead commented Oct 20, 2016

@mholo65 Depending on available time 😄 , feature freeze is planned for this weekend.

@bjorkstromm
Copy link
Member Author

@devlead ok, I'll see if I could dig it up til then!

@devlead
Copy link
Member

devlead commented Oct 20, 2016

@mholo65 Perfect 👌

@gep13
Copy link
Member

gep13 commented Oct 24, 2016

@mholo65 thanks again for this contribution!

@gep13 gep13 closed this as completed Oct 24, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants