- 29 6月, 2022 1 次提交
-
-
由 Calm_1024 提交于
-
- 11 3月, 2021 1 次提交
-
-
由 mamingshuai 提交于
-
- 09 9月, 2020 1 次提交
-
-
由 wenjun 提交于
-
- 30 10月, 2019 1 次提交
-
-
由 John Lindgren 提交于
-
- 29 10月, 2019 2 次提交
-
-
由 mvandervoord 提交于
-
由 mvandervoord 提交于
Stopped supported -0 as a float output because (a) it is non-portable, only existing on some architectures and (b) relies on the undefined behavior of 1.0/0.0
-
- 25 10月, 2019 1 次提交
-
-
由 mvandervoord 提交于
- fixed ANSI (C89) issues, including #418
-
- 23 10月, 2019 1 次提交
-
-
由 John Lindgren 提交于
Converting RUN_TEST() from a macro to a function significantly reduces the size of the compiled binary. On amd64, the largest test runner in the test suite (testsample_DefaultsThroughCommandLine_runner.o) was reduced from 3.4 kB to 2.4 kB (stripped).
-
- 06 7月, 2019 1 次提交
-
-
由 Mark VanderVoord 提交于
Add TEST_MESSAGE for outputting messages without aborting a test and _MESSAGE variant to TEST_PASS collection.
-
- 12 5月, 2019 1 次提交
-
-
由 Fabian Zahn 提交于
-
- 21 4月, 2019 1 次提交
-
-
由 Dom Postorivo 提交于
-
- 15 4月, 2019 1 次提交
-
-
由 Dom Postorivo 提交于
-
- 13 4月, 2019 1 次提交
-
-
由 Dom Postorivo 提交于
-
- 01 2月, 2019 1 次提交
-
-
由 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
-
- 11 12月, 2018 1 次提交
-
-
由 Elliot Gawthrop 提交于
-
- 19 2月, 2018 3 次提交
-
-
由 Fabian Zahn 提交于
-
由 Fabian Zahn 提交于
-
由 Fabian Zahn 提交于
-
- 18 2月, 2018 4 次提交
-
-
由 Fabian Zahn 提交于
void flushSpy(int c) {} to: void flushSpy(void) {}
-
由 Fabian Zahn 提交于
-
由 Fabian Zahn 提交于
-
由 Fabian Zahn 提交于
-
- 08 11月, 2017 4 次提交
-
-
由 John Lindgren 提交于
-
由 John Lindgren 提交于
-
由 John Lindgren 提交于
-
由 John Lindgren 提交于
-
- 10 9月, 2017 1 次提交
-
-
由 balaksh 提交于
-
- 26 8月, 2017 2 次提交
-
-
由 John Lindgren 提交于
-
由 John Lindgren 提交于
The existing implementation was not very good: - It printed all very small values as "0.000000..." - It did not distinguish positive and negative zero - In some cases it printed extra garbage digits for single-precision values (e.g. 3.9e+30 was printed as 3.90000013+30) Tests have been updated to check that we now match printf("%.6g") for 1,000,000 randomly chosen values, except for rounding of the 6th digit.
-
- 14 5月, 2017 1 次提交
-
-
由 Dom Postorivo 提交于
-
- 28 3月, 2017 1 次提交
-
-
由 Mark VanderVoord 提交于
Starting to enforce our coding style. The first step is that we’ve pulled in Rubocop to check out Ruby syntax. There is likely a bit of customization to do yet AND there is definitely that backlog of todo’s that we just told it to ignore.
-
- 22 3月, 2017 5 次提交
-
-
由 Mark VanderVoord 提交于
-
由 Mark VanderVoord 提交于
-
由 Mark VanderVoord 提交于
-
由 Mark VanderVoord 提交于
-
由 Mark VanderVoord 提交于
-
- 24 1月, 2017 1 次提交
-
-
由 jsalling 提交于
Correct clean target and print test fails during coverage in Makefile
-
- 15 1月, 2017 1 次提交
-
-
由 jsalling 提交于
Using this option changes the control flow of Unity, but is useful on constrained embedded systems. You can't fully simulate the power of 'longjmp' with just 'return', but Unity still works well, all tests pass.
-
- 30 12月, 2016 2 次提交
-
-
由 jsalling 提交于
-