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

Use api_data.py to generate what fields test/format should include in its fuzzer

    • Type: Icon: Improvement Improvement
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Test Format
    • None
    • Storage Engines
    • 5
    • StorEng - Defined Pipeline

      Currently, test/format relies on config.sh to know what fields to include in its fuzzer.

      Whenever api_data.py is updated with new fields, we need to update config.sh as well to take into account those new fields and make sure test/format use them (examples: WT-11348 / WT-12978.). This work could be avoided in config.sh would rely on api_data.py. Indeed, as soon as new a field would be added, test/format would be aware of it.

      One thing to be aware of though - api_data.py contains lots of different fields that test/format may not need to play with.

            Assignee:
            backlog-server-storage-engines [DO NOT USE] Backlog - Storage Engines Team
            Reporter:
            etienne.petrel@mongodb.com Etienne Petrel
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: