Actor name representing the user role performing authentication.
Examples: "admin", "user", "guest", etc. Each actor has different permissions and access scopes, requiring separate authorization functions.
Authentication type - one of "login" | "join" | "refresh" | "management".
The complete source code content of the test function. Contains the full implementation including function signature and body.
OpenAPI endpoint specification that this authorization function corresponds to.
Used to determine which endpoint this authorization function was generated from. For example, a login authorization function is generated from POST /auth/login endpoint.
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.
Discriminator field that identifies the specific type of test function. Used for discriminated union pattern to distinguish between different test function types.
Interface defining authorization functions used in test code.
Defines functions that perform authentication processes such as login, signup, and token refresh for each actor (user role) during E2E test execution. This interface is used by AutoBE to represent the structure and content of authorization functions when generating test code.
Author
Michael