Skip to content

Benchmark and stress testing in e2e tests #187

@ahmedwaleedmalik

Description

@ahmedwaleedmalik

We would like to make benchmarking and stress testing part of our e2e testing pipelines so that we can determine early if some code changes are causing any performance bottlenecks.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions