[SERVER-56192] Improve diagnosability of query planner unit tests Created: 20/Apr/21  Updated: 29/Oct/23  Resolved: 21/May/21

Status: Closed
Project: Core Server
Component/s: Query Planning, Testing Infrastructure
Affects Version/s: None
Fix Version/s: 5.1.0-rc0

Type: Task Priority: Major - P3
Reporter: Charlie Swanson Assignee: Timour Katchaounov
Resolution: Fixed Votes: 0
Labels: quick-tech-debt
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Sprint: Query Optimization 2021-05-17, Query Optimization 2021-05-31
Participants:

 Description   

The query planner unit tests often assert that a query solution is produced and use some custom JSON form to describe the expected query plan. This is often hard to get right when authoring a new test and it unfortunately does not provide much info about what mismatched if you don't get it exactly right. This patch gives a proof-of-concept of what we may be able to do to improve the experience for developers.



 Comments   
Comment by Vivian Ge (Inactive) [ 06/Oct/21 ]

Updating the fixversion since branching activities occurred yesterday. This ticket will be in rc0 when it’s been triggered. For more active release information, please keep an eye on #server-release. Thank you!

Comment by Githook User [ 21/May/21 ]

Author:

{'name': 'Timour Katchaounov', 'email': 'timour.katchaounov@mongodb.com'}

Message: SERVER-56192 Improve diagnosability of query planner unit tests

Generated at Thu Feb 08 05:38:37 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.