You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
How hard would it be to add different display options to organize the final report? As of now it's organized by each function call, but it would be nice to see a report broken down by function arguments.
Say I write a test suite calling function foobar with a bunch of different arguments, it would be nice to see how well that function scales depending on what's passed to it. Right now the only way to do this is to write a bunch of separate tests and run each in isolation. This is particular clumsy with hardhat mocha as well because running a single test is not easy from the command line.
Would be nice to be able to run the whole suite and see a detailed report of function breakdown by args. Other possibilities are to have a report breakdown per test function vs. for the whole suite (though not sure how easy it is to split metrics that way).
The text was updated successfully, but these errors were encountered:
cgewecke
changed the title
Add different display options?
Organize report by function arguments
Mar 14, 2024
How hard would it be to add different display options to organize the final report? As of now it's organized by each function call, but it would be nice to see a report broken down by function arguments.
Say I write a test suite calling function foobar with a bunch of different arguments, it would be nice to see how well that function scales depending on what's passed to it. Right now the only way to do this is to write a bunch of separate tests and run each in isolation. This is particular clumsy with hardhat mocha as well because running a single test is not easy from the command line.
Would be nice to be able to run the whole suite and see a detailed report of function breakdown by args. Other possibilities are to have a report breakdown per test function vs. for the whole suite (though not sure how easy it is to split metrics that way).
The text was updated successfully, but these errors were encountered: