To start this is just a shell for the test, there's no checking logic yet.. put it as `test_accounting.test_ib_account_with_duplicated_mktids()`. The test is composed for now to be completely runtime-free using only the offline txn-ledger / symcache / account loading APIs, ideally we fill in the activated symbology-data-runtime cases once we figure a sane way to handle incremental symcache updates for backends like IB.. To actually fill the test out with real checks we still need to, - extract the problem account file from my ib.algopape into the test harness data. - pick some contracts with multiple fqmes despite a single bs_mktid and ensure they're aggregated as a single `Position` as well as, * ideally de-duplicating txns from the account file section for the mkt.. * warning appropriately about greater-then-one fqme for the bs_mktid and providing a way for the ledger re-writing to choose the appropriate `<venue>` as the "primary" when the data-symbology-runtime is up and possibly use it to incrementally update the IB symcache and store offline for next use? |
||
---|---|---|
.. | ||
_inputs | ||
conftest.py | ||
test_accounting.py | ||
test_cli.py | ||
test_docker_services.py | ||
test_ems.py | ||
test_feeds.py | ||
test_questrade.py | ||
test_services.py | ||
test_watchlists.py |