A pytest-based Python port of the separate doselect/do-api-automation suite (DoSelect Recruit/Interview/Hacker/Contest/DOIQ/public APIs) into a layered spec-builder/response-handler/ model/test framework — see do-api-automation port below.

This is a first-pass port, scoped deliberately narrow. It sits as a sibling of the existing Java project and does not touch it.

Reporting: Serenity's Serenity.recordReportData() tabular summary convention is mirrored via src/reports/report_utils.py's log_test_summary(title, rows), which attaches an aligned text table (Input | Expected Status | Actual Status | Field Check | Result) to the Allure report.

cd python-api-automation
pip install -e .
pytest --alluredir=allure-results

To view the Allure report (requires the Allure command-line tool, installed separately — not a Python package):

allure serve allure-results

If the Allure CLI/Java aren't available, generate a self-contained HTML report instead (no extra tooling beyond pytest-html, already in dependencies):

pytest --html=report.html --self-contained-html

Open report.html directly in a browser.

The whole of doselect/do-api-automation (a flat, procedural pytest suite for DoSelect's Recruit/Interview/Hacker/Contest/DOIQ/AI-Interview/ Content-Creator and public APIs) rebuilt into this repo's layered spec-builder/response-handler/ model/test framework, extended to also cover session-cookie auth.

Full file-by-file status: DO_API_PORT_STATUS.md at the repo root tracks every source file's port status — this is the single source of truth for what's done. Everything is ported; a handful of files are deliberately-not-ported dead/duplicate code, documented in that file with the reasoning (see its tests/flows/ and utils/api_helper.py entries).

shared_data (a plain dict threaded through every source function call) is replaced throughout by explicit method parameters and return values — the same information flows, but through normal function signatures instead of a mutable grab-bag dict. Session-cookie-auth domains build a fresh AuthManager per test (no cross-test session reuse), matching the source exactly.

public_apis/problems, public_apis/invite, public_apis/fn (DoSelect-Api-Key/Secret header auth), regression/doiq, regression/ai_interview, regression/content_creator, regression/contest, regression/hacker, regression/interview, regression/recruit (session-cookie auth via AuthManager).

Needs the same environment variables as the source repo (BASE_URL, DOSELECT_API_KEY, DOSELECT_API_SECRET, DOSELECT_PRIMARY_DOMAIN, RECRUITER_EMAIL/RECRUITER_PASSWORD, etc. — see that repo's postactivate.sample) sourced into the shell before pytest runs. Without them, every ported test still collects cleanly but fails at request/login time (no live host to reach) — that's the expected "no credentials" mode, not a port defect.

pytest -m regression        # session-cookie-auth domains
pytest -m public             # public_apis/* (API-key auth)
pytest tests/regression/doiq tests/public_apis  # run specific domains directly

API automation runs on Jenkins at https://jenkins.chash.co/, on the same API-Automation job do-api-automation uses: https://jenkins.chash.co/job/QA/job/API-Automation/.

To trigger a build, open the job and use Build with Parameters.

The pipeline (Jenkinsfile) checks out the repo, creates a venv and installs requirements.txt, then runs test.sh, which:

1. Stashes the previous build's Allure history/ so trend charts carry over between runs.
2. Runs the initial pytest -n auto -m "$TAG_NAME" pass.
3. Optionally reruns only the failed tests (RERUN=true).
4. Merges both runs into one consolidated Allure report plus a single-file HTML report.
5. Emails the report (CSV summary + single-file HTML) to the opted-in recipients in reporting/email_list.csv, via send_email_report.py.

• Allure: published from reports/ by the Allure Jenkins Plugin, and the single-file HTML report is also published via the HTML Publisher plugin as a fallback.
• Credentials: postactivate-prod.sh/postactivate-dev.sh are gitignored and must already exist on the Jenkins agent with real values filled in (placed there manually, not part of this repo's checkout) — same approach as do-api-automation.