testrunner: show text-calldata on failing dispatch tests#473
Open
axic wants to merge 1 commit into
Open
Conversation
Add a text-calldata description to every dispatch test case (folding existing comment fields into it) and print it from the testrunner whenever a test fails, so failures identify which call was exercised. Co-authored-by: Alex Beregszaszi <alex@rtfs.hu>
axic
commented
Jun 16, 2026
| auto kind = test["kind"].get<std::string>(); | ||
|
|
||
| // Human-readable description of the call, shown when the test fails. | ||
| std::string const textCalldata = test["input"].value("text-calldata", std::string{}); |
Contributor
Author
There was a problem hiding this comment.
text-calldata is still optional, should it be mandatory?
Contributor
Author
There was a problem hiding this comment.
And should it be text-calldata or comment?
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
If a test case fails, display the
text-calldatanext to it for easier debugging, example:Or in this case I added
revertEmpty()in to the constructor: