Extend test suite to test different configurations
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 122
- Forks
- 34
- PR merge metrics
- No merged PRs in 30d
Description
As we start to have configuration parameters that enable/disable capabilities or new optimizations, we should be sure our test suite runs through all combinations. Note that this is complicated in that some test cases may no longer work, or the expected behavior may change.
For example, we may have a configuration option that changes whether stat() returns 0, local size, or the current global size pre-lamination. The test cases that check file size with stat will need to know this and know to check the correct expected value under each configuration.
- Test with shared memory only, no spill over
- Test with spill over only, no shared memory storage
- Test with both shared memory and spillover, with data sizes to utilize both
- Test with and without client write flattening
- Test with and without client reads via local extents
- Test with and without server reads via local extents
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the existing test suite and configuration controls for shared memory, spillover, client write flattening, and local extents. Run the relevant tests across the listed combinations, update cases whose behavior or expected file sizes vary by configuration, and verify every combination passes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- operating-systems, testing-qa
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100