Uploaded image for project: 'WiredTiger'
  1. WiredTiger
  2. WT-13388

block_ext unit tests - Part 1

    • Type: Icon: Task Task
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Block Manager
    • None
    • Storage Engines
    • 8
    • 2024-08-06 - Withholding Tax, 2024-09-03 Q3 Streams v1
    • The resolution should be: split into multiple PRs (see "split to" links) and replaced by them.

      The basic foundation of internal module testing starts from the bottom layer and with the block manager, this means creating unit tests. This ticket is to aim to unit test the relevant block_ext functions used for the block manager module. This ticket will create unit tests for:

      • This ticket - All tests pass
        • __block_off_srch_pair
        • __block_off_remove
        • __block_off_insert
        • __block_merge
        • __block_ext_insert
      • This ticket - One test fails - Product Bug
        • __block_off_match
      • Later tickets
        • __block_append
        • __block_extend
        • __wti_block_misplaced
        • __wti_block_alloc

      Note, these test cases are normal function tests. Error testing, if applicable for the function, are not included. I wanted to get the normal tests done for all before adding error testing.

      The definition of done, will be thoroughly testing the functions, with clear test cases working with the goal of increasing code coverage.

            Assignee:
            tod.johnson@mongodb.com Tod Johnson (Inactive)
            Reporter:
            jie.chen@mongodb.com Jie Chen
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: