Integration/e2e tests for etcd-wrapper component #4
Labels
area/quality
Output qualification (tests, checks, scans, automation in general, etc.) related
kind/enhancement
Enhancement, improvement, extension
lifecycle/rotten
Nobody worked on this for 12 months (final aging stage)
What would you like to be added:
Integration and/or e2e tests for etcd-wrapper, so that PRs and releases are thoroughly tested before integrating into etcd-druid.
Why is this needed:
Without integration tests running on etcd-wrapper, it is possible that a PR that works fine within etcd-wrapper may fail to play well with
etcd-backup-restore
when integrated into etcd-druid. It is better to catch it early, within etcd-wrapper itself, with the help of integration/e2e tests running on every PR and release./area quality
The text was updated successfully, but these errors were encountered: