Implement Verbose Support - #122
Conversation
|
I suggest to remove the argument |
|
That is to be determined. There are also Also, I'm having second thoughts about this. Instead of using a make command, maybe we could add a configuration argument to toggle the verbose output on and off for each run. This would prevent the need to recompile every time. Clearly, Make's build system isn't smart enough to automatically track macro changes and rebuild the affected files. However, I know CMake's build system is smart enough to recognize that a single macro definition change via the CLI requires rebuilding only the affected files. |
98665c8 to
72a174d
Compare
|
I ran the tests with and without verbose logging to check the difference in the time it took to complete when using a macro versus a config variable. Here is what I got from the hardware while testing the XeLoadSection function: macro verbose:
macro no verbose:
config verbose:
config no verbose:
Support for timing each test will be submitted in a separate pull request, which will add a new config option. |
72a174d to
a5db85d
Compare
|
I still don't like having to pass the API test name to |
Instead of always outputting a plain "PASSED" to the screen and the log file without any details, I added support for a
disable-verboseconfig option to theconfig.txtfile (which currently defaults to OFF). Enabling verbose logging provides deep details about what each test processed. This helps improve testing by ensuring that the written code works correctly, or by catching cases where a developer forgot to upload the updated XBE file.Developers or testers can disable verbose output by setting
disable-verbose=1in the config.txt file.