-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Fix some problems in the pytest adapter. #5648
Fix some problems in the pytest adapter. #5648
Conversation
c90c1c4
to
4bfc859
Compare
4bfc859
to
0762284
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Over all good, with few changes:
- Please remove
TODO
or add issues for them. - When raising exceptions, please add messages so one doens't need to figure out why the exceptions were thrown.
- Please document the JSON that's returned by this test adapter. This was requested in another PR but still not done. As a user of this code, I don't want to read multiple parts of the code to figure out what's being returned and the structure of the over all JSON (& possible values).
Any reason for not addressing the following:
|
traceback.print_stack() | ||
|
||
msg = 'Unexpected pytest node (see printed output).' | ||
exc = NotImplementedError(msg) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we really need to create a variable for this? Feels rather unnecessary.
Why not just inline this string?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No need to change.
(for #5458)
This is part of the effort to ensure that the pytest adapter can cope with unexpected circumstances (e.g. tests produced by third-party pytest plugins).
Note that this supercedes #5491.
[ ] Has a news entry file (remember to thank yourself!)[ ] Has sufficient logging.[ ] Has telemetry for enhancements.[ ] Test plan is updated as appropriate[ ]package-lock.json
has been regenerated by runningnpm install
(if dependencies have changed)[ ] The wiki is updated with any design decisions/details.