Skip to content

queued test status #402

@jason-gilroy-eb

Description

@jason-gilroy-eb

Is there any appetite for a "queued" test status?

My use case would be for submitting performance tests as a batch (for the purposes of this discussion, multiple tests that would exercise the same service.) Obviously, we'd want to measure the performance of the service for one test at a time; we don't want all the tests running at once.

A new configuration would be introduced for MAX_LOAD_TESTS_RUN (for my use case, this would be 1) and tests created in excess of this number of active tests (i.e. tests with "creating", "starting", "running" status) would be put into a new status "queued." When a test finishes, queued tests would be processed for possible promotion to an active test.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions