PXIL Session + Trading Token Setup Diagram

How configuration is called

pytest parametrization calls get_setup_configs("combined") when test_session_and_token_setup is collected.
get_product_config merges product overrides into setup.run_session/run_token and resolves token settings; disabled products are filtered out.
Each selected config carries url, login, product.me_instance, token settings and product_name into the test.

Combined run semantics

The test opens the portal and logs in once per browser fixture. It saves a browser cookie/session backup after login.
When run_session is true, create_session selects the configured ME instance and saves the calculated start/end window.
The same driver then loops product codes and calls run_token_setup for each one.

Token branches

IDAS/default creates the token, fills delivery/expiry values, then edits ORDER_NOR, ORDER_EXCH and TRADE time sessions before Save and Activate.
RTM selects market/product/generation mode, fills delivery and session times, then saves; activation is not part of this branch.
UPC fills configured order/trade times, saves, then resets the generator.

Authentication and evidence

login() sends credentials, waits for manual CAPTCHA completion, submits, waits for the dashboard marker and closes transient notices.
StepActions captures screenshots after interactions. conftest.py attaches them to pytest-html and creates report folders.
The diagram shows trading sessions/tokens; login session backups are browser cookies, not the trading-session records created in the portal.