Skip to content

Conversation

@yudov-maksim
Copy link
Contributor

Checkrange unit tests existed as 3 (for ydb based disks, nrd, mirror) almost identical test suits. Now it was moved into the one codebase as a part of volume_ut tests with disk's type as a parameter for test case.
Comparing to previous code, tests have only minor changes. Logically it is almost the same.
"Almost" - for example, we had test with logical error. "ShouldGetSameChecksumsWhileCheckRangeSimmilarDisks" was designed to check writing to 2 disks, but it was done into one disks with 2 clients. This testcase was replaced by different, but logically similar "DoTestShouldGetSameChecksumsWhileCheckRangeEqualBlocks" test.

// This refactoring has done as a part of checkrange utility improvements.

@github-actions
Copy link
Contributor

github-actions bot commented Dec 4, 2025

Note

This is an automated comment that will be appended during run.

🔴 linux-x86_64-relwithdebinfo: some tests FAILED for commit 01e6d44.

TESTS PASSED ERRORS FAILED FAILED BUILD SKIPPED MUTED?
9658 9656 0 1 0 1 0

🟢 linux-x86_64-relwithdebinfo: all tests PASSED for commit 01e6d44.

TESTS PASSED ERRORS FAILED FAILED BUILD SKIPPED MUTED?
45 45 0 0 0 0 0

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.

2 participants