test-case-generator

Provide the Meeting Server interface documentation, PRD, or UI prototype as input, and the Skill outputs structured test cases with 8-field tables and agent-executable YAML blocks. Each case covering an existing meeting automatically includes login, meeting creation, and cleanup steps.

All login steps read credentials exclusively from the TEST_ACCOUNT and TEST_PASSWORD environment variables, never hardcoded literals. Python mode uses os.environ lookups and skips the case if the variables are unset; Markdown mode declares the requirement in preconditions.

Dating setup meetings on the next month's first day keeps them far in the future, preventing business rules like 'ongoing meetings cannot be deleted' from blocking teardown. Near-term relative dates like today+2 historically caused cleanup failures and leftover data.

Yes, Python mode produces pytest files using login_creds and created_meeting fixtures with yield-based teardown that deletes meetings even when assertions fail. It uses requests, the cryptography library for RSA password encryption, and stdlib datetime for date calculation.

The teardown block always runs with always_run: true and attempts deletion with ignore_errors: true, accepting 200 or 404. This double safety net ensures no orphaned meetings remain even when the tested delete already succeeded or the case errored.

It only produces Meeting Server test cases and refuses unrelated requests. It requires known inputs like the API host, path prefix, and meeting field constraints; missing information halts generation rather than guessing, and concurrency cases require Python mode.