Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature] Move performance regression tests into the test machinery integration test suite #281

Open
amshuman-kr opened this issue Nov 3, 2020 · 0 comments
Labels
kind/enhancement Enhancement, improvement, extension lifecycle/rotten Nobody worked on this for 12 months (final aging stage) priority/4 Priority (lower number equals higher priority)

Comments

@amshuman-kr
Copy link
Collaborator

Feature (What you would like to be added):
[Feature] Move performance regression tests into test machinery integration test suite

Motivation (Why is this needed?):
Tests get executed automatically during PR merge.

Approach/Hint to the implement solution (optional):
The tests are ginkgo and gomega based.

@amshuman-kr amshuman-kr added the kind/enhancement Enhancement, improvement, extension label Nov 3, 2020
@gardener-robot gardener-robot added the lifecycle/stale Nobody worked on this for 6 months (will further age) label Sep 22, 2021
@gardener-robot gardener-robot added lifecycle/rotten Nobody worked on this for 12 months (final aging stage) and removed lifecycle/stale Nobody worked on this for 6 months (will further age) labels Mar 24, 2022
@abdasgupta abdasgupta added the priority/4 Priority (lower number equals higher priority) label Jan 5, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/enhancement Enhancement, improvement, extension lifecycle/rotten Nobody worked on this for 12 months (final aging stage) priority/4 Priority (lower number equals higher priority)
Projects
None yet
Development

No branches or pull requests

3 participants