Simpler API for table outputs - #55
Open
Julow wants to merge 5 commits into
Open
Conversation
dinosaure
force-pushed
the
analyze_to_table
branch
from
April 16, 2026 12:49
312f31b to
37ad7a0
Compare
This function analyze the test results and present them in a tabular format for easier CSV or json output.
dinosaure
force-pushed
the
analyze_to_table
branch
from
April 16, 2026 13:00
37ad7a0 to
0f89357
Compare
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
2 participants
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.
I wanted to save the benchmark results into a CSV and found that it was quite difficult to deal with the current API.
The code in the examples folder uses the
mergefunction, which has a confusing signature. On top of that, it looses the list of test names, which makes creating a CSV output harder and error prone.I struggled quite a bit to get a correct CSV output, so I figured that it would be worthwhile to support this usecase in the library.
Maybe related to #53