ticket-lifecycle-check

Automate end-to-end ticket lifecycle testing by running Pytest with Playwright to verify ticket creation, editing, status changes, search, and deletion across UI and API layers. Execute tests from the Python virtual environment to validate complete CRUD operations.

Ticket lifecycle validation verifies the complete flow of tickets including creation, editing, status changes, and deletion. You need it when testing ticket management modules to ensure UI and API layers handle CRUD operations correctly and reproducibly.

Yes, ticket management testing requires a frontend running at http://localhost:3000 and a backend API. You also need a Python 3 environment with Playwright and Pytest installed and the virtual environment at tests/e2e/venv activated.

Yes, ticket lifecycle tests support reproducible execution for QA and CI pipelines. Run pytest -s tests/e2e/test_tickets_full.py within the virtual environment to automate verification of login, navigation, creation, editing, and deletion workflows.

The best way to verify ticket status changes across UI and API layers is using end-to-end testing with Playwright and Pytest. This approach validates status transitions through both interface layers within a single automated test run for comprehensive coverage.

Ticket lifecycle tests fail if the Python virtual environment at tests/e2e/venv is not activated or Playwright and Pytest are not installed. Ensure the frontend at http://localhost:3000 and backend API are running before executing tests.