[SERVER-47853] Add unit tests which combine diffing algorithm and application code Created: 30/Apr/20 Updated: 29/Oct/23 Resolved: 07/Jul/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Querying |
| Affects Version/s: | None |
| Fix Version/s: | 4.7.0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Ian Boros | Assignee: | Arun Banala |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | qexec-team | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Query 2020-06-15, Query 2020-06-29, Query 2020-07-13 |
| Participants: |
| Comments |
| Comment by Githook User [ 07/Jul/20 ] |
|
Author: {'name': 'Arun Banala', 'email': 'arun.banala@mongodb.com', 'username': 'banarun'}Message: |
| Comment by Ian Boros [ 03/Jun/20 ] |
|
Random thought about one way to do this: We could define a small "corpus" of documents (maybe 20-30). Then we take a random "walk" through those a subset of them. We produce a diff for each step of the walk (one diff when going from i -> j, another when going from j -> k, etc). Then at the end, we re-apply the entire sequence of diffs to each document we visited along the walk, and check that we always get the same post image. To get more interesting cases we might also want to add a flag/option to the diffing code which prevents it from bailing out. |