1. 03 7月, 2019 2 次提交
  2. 27 6月, 2019 2 次提交
  3. 05 5月, 2019 2 次提交
  4. 04 5月, 2019 13 次提交
  5. 21 4月, 2019 2 次提交
  6. 15 4月, 2019 1 次提交
  7. 14 4月, 2019 3 次提交
  8. 13 4月, 2019 1 次提交
  9. 08 4月, 2019 1 次提交
  10. 07 4月, 2019 1 次提交
  11. 04 4月, 2019 1 次提交
  12. 27 3月, 2019 1 次提交
  13. 26 3月, 2019 1 次提交
  14. 25 3月, 2019 1 次提交
  15. 24 3月, 2019 1 次提交
  16. 12 3月, 2019 2 次提交
  17. 22 2月, 2019 2 次提交
  18. 20 2月, 2019 1 次提交
  19. 19 2月, 2019 1 次提交
  20. 01 2月, 2019 1 次提交
    • E
      Improvements to the execution time feature · 076f0fff
      elliot 提交于
      - Running time macros have been made more portable, previously it was not
        possible to override all macros
      - Running time macros will be executed by default test runner, and auto test
        runners
      - Adds a default execution time implementation for unix. (Previous default
        implementation only worked on Windows)
      - For embedded platforms there is a simple method of getting a default
        implementation by defining a single macro UNITY_CLOCK_MS()
      - Removed need for UNITY_EXEC_TIME_RESET. This was not being used for the default
        implementations, if anything ever did need reset-like functionality it could
        simply be wrapped up with the start or stop macros for that platform
      076f0fff