Skip to content

test(e2e): rely on precheck for DataExport availability#2499

Open
eofff wants to merge 1 commit into
mainfrom
chore/remove-data-export-skip
Open

test(e2e): rely on precheck for DataExport availability#2499
eofff wants to merge 1 commit into
mainfrom
chore/remove-data-export-skip

Conversation

@eofff

@eofff eofff commented Jun 17, 2026

Copy link
Copy Markdown
Contributor

Description

Remove the runtime skip from the DataExports e2e suite that checked whether the storage-volume-data-manager module is enabled.

The suite already has PrecheckSVDM and PrecheckDataExport labels, so the environment suitability should be handled by prechecks before the test starts.

Why do we need it, and what problem does it solve?

The test duplicated module availability validation in BeforeEach and silently skipped execution when storage-volume-data-manager was disabled.

Prechecks are enough for this condition, and keeping the skip in the test hides configuration issues from the precheck layer.

What is the expected result?

DataExports e2e tests are selected or rejected by the existing prechecks. The test code no longer performs an additional skip based on the storage-volume-data-manager module state.

Checklist

  • The code is covered by unit tests.
  • e2e tests passed.
  • Documentation updated according to the changes.
  • Changes were tested in the Kubernetes cluster manually.

fix
Signed-off-by: Valeriy Khorunzhin <valeriy.khorunzhin@flant.com>
@eofff eofff requested a review from Isteb4k as a code owner June 17, 2026 08:44
@eofff eofff added this to the v1.10.0 milestone Jun 17, 2026
@eofff eofff requested a review from hardcoretime June 17, 2026 09:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant