[SERVER-62330] ABT testing infrastructure Created: 31/Dec/21 Updated: 06/Dec/22 Resolved: 13/Jul/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Nicholas Zolnierz | Assignee: | Backlog - Query Optimization |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Query Optimization
|
||||||||
| Sprint: | QO 2022-02-07 | ||||||||
| Participants: | |||||||||
| Description |
|
This ticket is ambiguous at the time of writing, but the motivation is to update the unit tests from the fuzzer to avoid large string comparisons on ABT dumps. Some ideas from the design:
|
| Comments |
| Comment by Hana Pearlman [ 13/Jul/22 ] |
|
As decided in design review and some other meetings, we'll use golden testing to handle ABT translation unit tests. I think that mostly takes away the need for this ticket, so I'm closing in favor of |