1. 04 9月, 2016 2 次提交
  2. 01 9月, 2016 3 次提交
  3. 28 8月, 2016 1 次提交
  4. 26 8月, 2016 1 次提交
  5. 24 8月, 2016 1 次提交
  6. 06 5月, 2016 1 次提交
  7. 04 5月, 2016 6 次提交
  8. 26 4月, 2016 1 次提交
  9. 25 4月, 2016 1 次提交
    • J
      Revert commits 720ea42a and a27b03c7 which broke the Fixture build · 57348172
      jsalling 提交于
       These were aimed at preventing the internals header from declaring
        a prototype for 'int UNITY_OUTPUT_CHAR(int);'. The second part fixed
        an omitted declaration in the tests caused by the first commit.
       Will replace the default behavior & add an option for this in next commit
      57348172
  10. 13 4月, 2016 1 次提交
  11. 03 3月, 2016 1 次提交
  12. 26 2月, 2016 1 次提交
    • J
      Delete function call syntax from Spy detect macros · f55bed38
      jsalling 提交于
       This fixes #168. See that github.com issue for more discussion.
       Allows the tests to build when putchar() is defined as a macro
        with parenthesis around it, as in the ARM embedded gcc compiler.
      f55bed38
  13. 25 2月, 2016 1 次提交
  14. 13 2月, 2016 1 次提交
  15. 07 1月, 2016 2 次提交
  16. 21 12月, 2015 1 次提交
    • J
      Add tests for printing numbers using a compile time replacement spy · a3d81dfa
      jsalling 提交于
       If Unity core is compiled with UNITY_OUTPUT_CHAR = putcharSpy, these tests
        will run, otherwise they are ignored and print a message
       Includes an implementation of putcharSpy, which allows checking the I/O
        from Unity during a test. Follows closely from the Fixture spy
       Tricky macros determine if putcharSpy is injected
      a3d81dfa
  17. 11 12月, 2015 1 次提交
  18. 15 7月, 2015 1 次提交
  19. 24 4月, 2015 1 次提交
  20. 23 4月, 2015 1 次提交
  21. 02 9月, 2014 1 次提交
  22. 30 7月, 2014 1 次提交
  23. 23 7月, 2014 1 次提交
  24. 22 7月, 2014 2 次提交
  25. 23 5月, 2014 1 次提交
  26. 28 6月, 2013 2 次提交
    • A
      Fix tests testing TEST_ASSERT_EQUAL_MEMORY_ARRAY on 16-bit platforms · 2b484e42
      Antony Male 提交于
      The tests which exercise TEST_ASSERT_EQUAL_MEMORY_ARRAY use int arrays,
      and hard-code the size of each element as 4 bytes. This is of course
      untrue on 16-bit platforms.
      
      Replace this hard-coded value with sizeof(int).
      2b484e42
    • A
      Fix unit tests for TEST_ASSERT_EQUAL_HEX_ARRAY on 16-bit architectures · 318dc8f3
      Antony Male 提交于
      Previously, TEST_ASSERT_EQUAL_HEX_ARRAY was being called, and passed
      arrays of type 'unsigned int'. TEST_ASSERT_EQUAL_HEX_ARRAY is an alias
      for TEST_ASSERT_EQUAL_HEX32_ARRAY in *all* cases (and is documented as
      such), while 'unsigned int' is 16 bits on some platforms. Unsurprisingly
      this caused some tests to fail.
      
      Fix by replacing the 'unsigned int' declarations with '_UU32'.
      318dc8f3
  27. 27 11月, 2012 1 次提交
  28. 31 10月, 2012 2 次提交