[SERVER-49014] Add additional timestamping tests to the KVEngine test harness Created: 22/Jun/20 Updated: 29/Oct/23 Resolved: 14/Jul/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | 4.7.0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Gregory Wlodarek | Assignee: | Bynn Lee |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | intern_ephemeral_for_test | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Execution Team 2020-07-13, Execution Team 2020-07-27 |
| Participants: |
| Description |
|
The KVEngine test harness allows us to create a single set of unit tests that runs on multiple storage engines. In order to have a test-driven development approach for adding timestamp support for Biggie, we should add additional unit tests to the harness to increase our test coverage for the storage engines. We can deterministically identify what the timestamps (oldest, stable, all durable) should be set to after performing a set of operations. A few simple examples of unit tests could be:
Obviously, this isn't an extensive list and we should add more. |
| Comments |
| Comment by Githook User [ 14/Jul/20 ] |
|
Author: {'name': 'Bynn Lee', 'email': 'bynn.lee@mongodb.com', 'username': 'bynn'}Message: |