google / google/mobly

KeyboardInterrupt terminates log non-gracefully

Open
#498 5 comments 0 reactions 1 assignee Claimed by @xpconanfan View on GitHub
improvement
Dominant language
Python
Stars
752
Forks
222
Avg merge
14d 18h
Merged PRs (30d)
1

Description

After a testsuite is halted due to keyboardinterrupt, the ControllerInfo summary in the yaml log file will have 0 in all categories (even Requested) regardless of prior test results. Also, the current test will have mostly null values recorded, and any unrun testcases will not have entries.

It would be nice if all results received prior to the interrupt were properly recorded.
It would also be nice if all the tests that never got to be started were listed as skipped with an appropriate explanation.
Finally it's up to you whether or not the current test should have an explicit fail, a skip, or leave it with the nulls, since any of those is a more subjective choice (can the test really be said to 'fail' when it was interrupted? Perhaps not). But it would be nice if the current test log entry mentioned in some way that it stopped due to a keyboard interrupt and not due to its own or Mobly's fault.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.