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.

Sign up for GitHub

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

Jump to bottom

[Tests] Optimise the tests #125

Open
swapnilgm opened this issue Feb 19, 2019 · 1 comment
Open

[Tests] Optimise the tests #125

swapnilgm opened this issue Feb 19, 2019 · 1 comment
Labels
area/dev-productivity Developer productivity related (how to improve development) component/etcd-backup-restore ETCD Backup & Restore effort/2d Effort for issue is around 2 days exp/beginner Issue that requires only basic skills kind/test Test lifecycle/rotten Nobody worked on this for 12 months (final aging stage) platform/all priority/3 Priority (lower number equals higher priority) status/accepted Issue was accepted as something we need to work on

Comments

@swapnilgm
Copy link
Contributor

swapnilgm commented Feb 19, 2019 •
edited
Loading

Feature (What you would like to be added):
Create scalable and reusable test framework for testing. Optimise the time consumed for running all the tests.

Motivation (Why is this needed?):
Currently, we have duplicate code used for setting up environment like bootstrapping etcd or pushing test specific data to etcd. Now its causing extra time consumption while running tests. We are not able to run many tests in parallel. Thorough the experience we now have enough idea to make generic and reusable code.
@swapnilgm swapnilgm added kind/enhancement Enhancement, improvement, extension exp/beginner Issue that requires only basic skills area/dev-productivity Developer productivity related (how to improve development) size/s Size of pull request is small (see gardener-robot robot/bots/size.py) component/etcd-backup-restore ETCD Backup & Restore platform/all kind/test Test priority/normal and removed kind/enhancement Enhancement, improvement, extension labels Feb 19, 2019
@gardener-robot-ci-1 gardener-robot-ci-1 added lifecycle/stale Nobody worked on this for 6 months (will further age) and removed lifecycle/stale Nobody worked on this for 6 months (will further age) labels Apr 22, 2019
@gardener-robot-ci-1 gardener-robot-ci-1 added lifecycle/stale Nobody worked on this for 6 months (will further age) and removed lifecycle/stale Nobody worked on this for 6 months (will further age) labels Jun 25, 2019
@swapnilgm swapnilgm self-assigned this Aug 12, 2019
@swapnilgm swapnilgm mentioned this issue Aug 30, 2019
Merged
@gardener-robot-ci-2 gardener-robot-ci-2 added lifecycle/stale Nobody worked on this for 6 months (will further age) and removed lifecycle/stale Nobody worked on this for 6 months (will further age) labels Oct 12, 2019
@ghost ghost added lifecycle/stale Nobody worked on this for 6 months (will further age) and removed lifecycle/stale Nobody worked on this for 6 months (will further age) labels Dec 12, 2019
@ghost ghost added lifecycle/stale Nobody worked on this for 6 months (will further age) and removed lifecycle/stale Nobody worked on this for 6 months (will further age) labels Feb 11, 2020
@ghost ghost added the lifecycle/stale Nobody worked on this for 6 months (will further age) label Apr 15, 2020
@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 Jun 29, 2020
@gardener-robot gardener-robot added priority/3 Priority (lower number equals higher priority) effort/2d Effort for issue is around 2 days and removed priority/normal size/s Size of pull request is small (see gardener-robot robot/bots/size.py) labels Mar 8, 2021
@abdasgupta
Copy link
Contributor

abdasgupta commented Jan 5, 2023 •
edited
Loading

Test coverages are increased and lots of unit test cases added using mock tests. But we need to explore if we can further optimize some test cases to run in parallel

@gardener-robot gardener-robot added the status/closed Issue is closed (either delivered or triaged) label Jan 5, 2023
@abdasgupta abdasgupta reopened this Jan 5, 2023
@gardener-robot gardener-robot added status/accepted Issue was accepted as something we need to work on and removed status/closed Issue is closed (either delivered or triaged) labels Jan 5, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/dev-productivity Developer productivity related (how to improve development) component/etcd-backup-restore ETCD Backup & Restore effort/2d Effort for issue is around 2 days exp/beginner Issue that requires only basic skills kind/test Test lifecycle/rotten Nobody worked on this for 12 months (final aging stage) platform/all priority/3 Priority (lower number equals higher priority) status/accepted Issue was accepted as something we need to work on
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@swapnilgm @abdasgupta @gardener-robot-ci-1 @gardener-robot-ci-2 @gardener-robot