start-qa

To automate QA session setup, the system scans framework configurations, Makefiles, and docker-compose files to discover startup procedures, then restarts the application and launches a browser for manual testing while monitoring health checks.

A qa-config.md file is a standardized configuration document that stores discovered startup, health-check, and logging procedures for a project. You need it to enable fast subsequent manual QA sessions without repeating the environment discovery process.

If no tasks/qa-config.md exists, the system performs a one-time startup discovery by scanning Makefiles, docker-compose, and package.json scripts to derive startup, health, and logging procedures, then generates the config file automatically.

Yes, the discovery process explicitly scans Makefiles, docker-compose files, package.json scripts, Procfiles, and framework configs to identify startup commands and health checks, making it compatible with diverse repository structures.

The best way is to load or discover the project's QA configuration, restart the application, and launch a browser session while running health and smoke checks in the background to monitor application liveness during testing.

QA session startup discovery may fail if the repository lacks standard startup sources such as Makefiles, docker-compose, package.json scripts, Procfiles, or recognizable framework configs, preventing the system from deriving startup and health-check procedures.