1. 16 12月, 2015 3 次提交
  2. 11 12月, 2015 4 次提交
  3. 08 12月, 2015 1 次提交
  4. 04 12月, 2015 1 次提交
  5. 24 11月, 2015 4 次提交
  6. 13 11月, 2015 2 次提交
  7. 11 11月, 2015 1 次提交
  8. 10 11月, 2015 1 次提交
  9. 29 10月, 2015 1 次提交
    • A
      define setUp and tearDown under UNITY_WEAK_PRAGMA · d4b83f18
      Andy Isaacson 提交于
      The intent of UNITY_WEAK_PRAGMA is that we have weak symbols for setUp
      and tearDown in unity.o, so that developers can override these symbols
      if needed but the link works right if they are not defined.
      
      In order to do this using #pragma, the pragma and the definition of the
      function (not the declaration) need to be present in the same translation
      unit (source code file).
      
      Previously, the UNITY_WEAK_PRAGMA code was just declaring the setUp
      function, but not defining it, which means that developers had to add an
      empty setUp function to their tests in order to link.
      d4b83f18
  10. 28 10月, 2015 2 次提交
  11. 15 10月, 2015 2 次提交
    • M
      Merge pull request #139 from jeremyhannon/master · e8968304
      Mark VanderVoord 提交于
      MISRA rule 19.10: parentheses around macro params
      e8968304
    • J
      MISRA rule 19.10: parentheses around macro params · 1273112a
      Jeremy Hannon 提交于
      Added parentheses around all macro parameters to resolve MISRA 2004
      rule 19.10, "in the definition of a function-like macro, each instance
      of a parameter shall be enclosed in parenthesis" as tested with the
      IAR EW for 8051 compiler, version 9.20.2.
      
      The only questionable change is in "unity_fixture.h" where the nested
      macro DECLARE_TEST_CASE in RUN_TEST_CASE prevents surrounding params
      "group" and "name" with parentheses.
      However, it appears that macro DECLARE_TEST_CASE isn't used elsewhere,
      so I eliminated DECLARE_TEST_CASE and put its expansion directly in
      RUN_TEST_CASE.  Now the following header files pass rule 19.10:
      * unity.h
      * unity_internals.h
      * unity_fixture.h
      
      For my own project, this change to the Unity test framework allows me
      to include my unit test code to be tested against MISRA rules as well,
      instead of just production code, to help enforce style and team
      guidelines.
      1273112a
  12. 06 10月, 2015 2 次提交
  13. 18 9月, 2015 2 次提交
  14. 18 8月, 2015 2 次提交
  15. 03 8月, 2015 2 次提交
  16. 29 7月, 2015 1 次提交
  17. 27 7月, 2015 1 次提交
  18. 22 7月, 2015 1 次提交
  19. 21 7月, 2015 4 次提交
  20. 15 7月, 2015 3 次提交