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.