Interface IAutoBeTestRuntimeProps

Optional flag indicating whether to perform a complete database reset before test execution.

When true, specifies that the test execution should begin with a comprehensive database reset, purging all existing data and reconstructing tables to their initial schema-defined state. When false, test execution proceeds with the current database state, which may contain residual data from previous operations.

Database reset is crucial for ensuring test isolation, reproducibility, and deterministic results. Clean state testing eliminates interference from residual data and guarantees that each test execution cycle operates under identical baseline conditions, enabling accurate validation of backend implementation behavior.

Optional specification of the maximum number of test functions to execute concurrently during the test suite run.

Defines the concurrent execution limit for E2E test functions to optimize testing performance while maintaining system stability and resource management. This value balances test execution speed with resource consumption and helps prevent system overload during comprehensive validation.

Concurrent execution significantly reduces total testing time for large test suites while validating the backend application's ability to handle parallel requests correctly. The simultaneous limit ensures controlled load conditions that provide meaningful performance insights while maintaining test reliability and result accuracy.