CHECK_PERFORMANCE macro is not complete
colinrg opened this issue · 3 comments
colinrg commented
This has only had an initial commit made with a draft and untested version, which is yet to be completed.
CHECK_TIME macro does work, but does not provide a success or fail status, but only logs time elapsed and number of iterations.
CHECK_PERFORMANCE will also provide a failure message when the number of iterations is less than is expected, which would indicate the function has become slower, or the environment has changes, such as performance of the computer running the tests.
colinrg commented
Plan is to get this working and tested by 1st of May 2016, and hopefully earlier, with performance tests written for TestStringUtility class.