The complete source code content of the test function. Contains the full implementation including function signature and body.
Business domain for test organization (e.g., "user", "order", "payment").
The file system location where this test function will be written. Should be an absolute or relative path to the target test file.
The name identifier of the function. Used to reference the function within the test suite.
Test scenario metadata (target endpoints, expected behavior, prerequisites).
Discriminator field that identifies the specific type of test function. Used for discriminated union pattern to distinguish between different test function types.
E2E test scenario function with domain classification.
Author
Michael