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
Andriy wants a test summary at the end of a HW tests, where he sees at a glance if the whole test passed or failed. I think that that's a great idea, and we should extend it to print a summary of how many checks passed/failed in total. For this, we need to change Check() to log the total number of passes and fails and print the results at the end of the thread. An RAII class called Test would be a good option for that. Its constructor takes a title/description that it prints at the beginning, and its destructor prints the summary at the end.
Something similar should be implemented for the unit tests that require Rodos as well. Of course, it would be best to implement one thing that can be used in both cases, but I am not sure if that's feasible because the HW tests need to do some things in the threads init() function while the Rodos unit tests just implement RunUnitTest() which is then called by the unit test thread's run() method.
Finally, it would be nice to have Check() and Require() for both kinds of tests.
The text was updated successfully, but these errors were encountered:
Description
Andriy wants a test summary at the end of a HW tests, where he sees at a glance if the whole test passed or failed. I think that that's a great idea, and we should extend it to print a summary of how many checks passed/failed in total. For this, we need to change
Check()
to log the total number of passes and fails and print the results at the end of the thread. An RAII class calledTest
would be a good option for that. Its constructor takes a title/description that it prints at the beginning, and its destructor prints the summary at the end.Something similar should be implemented for the unit tests that require Rodos as well. Of course, it would be best to implement one thing that can be used in both cases, but I am not sure if that's feasible because the HW tests need to do some things in the threads
init()
function while the Rodos unit tests just implementRunUnitTest()
which is then called by the unit test thread'srun()
method.Finally, it would be nice to have
Check()
andRequire()
for both kinds of tests.The text was updated successfully, but these errors were encountered: