Closed goodboy closed 1 year ago
test_runtime_boot
The log dumping to console is on purpose actually since we might want to assert a schema from those msgs eventually using pytest
's streams capture.
I will change the test for sure 👍🏼
You should add log level to test_runtime_boot as it's instantiation is logging at info by default. Also there is a bunch of market data being dumped in the console:
As per chat discussion, the issue isn't this test func since the fixture takes care of binding in the log level. So it's got to be an issue elsewhere (probably hardcoded info level?).
I'll check.
Yup, had to patch the clearing._client.open_ems()
to passthrough a loglevel: str
and then adjust the service tests to passthrough the fixture value.
All there now please review!
Looking good now @goodboy
Like it sounds, this jigs our test harness to include:
loglevel: str
session scoped fixture for downstream use, pulled directly from the--ll <level: str>
input by the user via CLIloglevel
value toopen_test_pikerd()
async mngr to allow controlling full service tree logging frompytest
CLIAlso included are some minor tweaks to remove some warnings from the summary, mostly to do with
tractor
API deprecations, and some moving of oldconftest
fixture code to thetest_questrade
module.