Current Testing Coverage for Verification consists of:
- Unit tests that invoke the wt verify wrapper.
- Implicit testing through other WT test cases that indirectly call wt verify (python suite, format testing, etc.)
Goal of This Ticket:
The objective is to investigate whether the current testing can be reused for DisAgg verification testing purposes.
As far as I know, there is no way to run the wt command-line utility with PALI. Therefore, we need to determine:
- Whether it is acceptable to test with PALM (at least initially):
-
- If so, how to properly set up and execute such tests.
- Do we want to support testing with PALI in the future, and if so, how can we achieve that?
Expected Outcome:
- Enable all suitable existing tests to check the DisAgg verification MVP implementation (
WT-14907).
- For any tests that cannot be reused for the PoC, identify the reasons why and propose how to address these testing gaps going forward.
Given that we now have the logic that reports successful validation for all DisAgg tables without actual checks (i.e., “plumbing” is not yet in place), I expect that at least the tests expecting positive verification results should pass.
- is related to
-
WT-15064 Add table corruptions detection test cases for DisAgg tables verification
-
- Open
-
-
WT-14907 DisAgg verification MVP implementation
-
- Closed
-
- related to
-
WT-15062 Investigate the need to support the `wt verify` utility for DisAgg tables
-
- Open
-
-
WT-14553 Support WT_SESSION->verify for layered tables
-
- Closed
-
-
WT-15034 DisAgg verification MVP testing
-
- Closed
-
-
WT-15035 DisAgg verification MVP productization
-
- Closed
-