-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: benchmark_list_tests benchmark-format=json #1647
base: main
Are you sure you want to change the base?
feat: benchmark_list_tests benchmark-format=json #1647
Conversation
This should not be added. My mistake
this file should not be added by me. test/ third_party / googletest / CMakeLists.txt
Now we have to add the test cases for this enhancement and also have to modify the console menu for this change. Line 729 in 1c64a36
and also the documentation =) or maybe we just need to modify the documentations and the test cases? |
@@ -164,6 +164,14 @@ class TestReporter : public benchmark::BenchmarkReporter { | |||
for (auto rep : reporters_) rep->Finalize(); | |||
} | |||
|
|||
void List(const std::vector<benchmark::internal::BenchmarkInstance>& |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
perhaps we could have a gtest for the List function?
Apologies, @dmah42 I am currently writing a book on ADHD and I didn't evaluate that it will take this much of time. I am trying to complete it soon and will work on the remaining issues. =) |
The basics
clang-format
The details
Resolves
Proposed Changes
To output the benchmark list in JSON format.
Behavior Before Change
Unable to get the desired output for the automation purpose in the JSN format.
Behavior After Change
Added the support for the use of
--benchmark_list_tests
together with--benchmark-format=json
.Reason for Changes
With this change, the user will be able to get the benchmark output easily in JSON format for better machine use cases.
Test Coverage
I haven't tested this, as soon as I got confirmation that these are the required changes that will update the status of the Test Coverage.
Documentation
Documentation needs to be done for this as it's a feature request once this will pass all the test cases I will add the required document for this.
Additional Information