wwakabobik / testrail_api_reporter / 39042850001

100%

push

github

Live TestRail test suite, fix run-lookup/skip-status/automation-id bugs found by it (#88)

* Fix run-lookup crash by name, add live TestRail test suite

- __search_for_run_by_name indexed response["runs"] (a list) as if it
  were a single run dict, so any real get_runs response (or matching
  mocked data) would raise TypeError. Reuse the existing __search_for_item
  helper instead, matching how cases are already searched; add a
  pagination regression test.
- Add tests/live/: opt-in, env-var-gated tests that exercise the real
  TestRail REST API end-to-end (results_reporter round trip, coverage
  reporter pagination, content generator case lookup, legacy suite
  export) instead of mocks. They skip cleanly when TESTRAIL_URL/EMAIL/
  PASSWORD/PROJECT_ID aren't set.
- Document that TCBackup's legacy web UI export needs a real account
  password, not an API key, unlike every REST-based class here.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01RQpugp1JRRd1Ch5tg2Kef1

* Resolve the skipped-test status id dynamically instead of hardcoding it

Non-xfail "skipped" pytest results were always mapped to status_id 7, which
assumes every TestRail instance has a custom status with that exact id -
true by convention on many Cloud accounts, but not guaranteed (a fresh
project/instance, like the one we're validating this library against,
won't have it). Resolve it by name/label via statuses.get_statuses()
instead, caching the result, with id 7 kept only as the last-resort
fallback when no matching status exists or the lookup fails.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01RQpugp1JRRd1Ch5tg2Kef1

* Make the automation-id case field name configurable, fix live KeyError

Found by running the live TestRail test suite against a real instance:

- __get_all_auto_cases crashed with KeyError when a case lacked the
  automation-id custom field entirely (pr... (continued)

393 of 400 branches covered (98.25%)

Branch coverage included in aggregate %.

32 of 32 new or added lines in 3 files covered. (100.0%)

1329 of 1329 relevant lines covered (100.0%)

12.0 hits per line