- 22 12月, 2018 1 次提交
-
-
由 Dom Postorivo 提交于
-
- 11 12月, 2018 1 次提交
-
-
由 Elliot Gawthrop 提交于
-
- 29 11月, 2018 1 次提交
-
-
由 John Lindgren 提交于
-
- 09 8月, 2018 1 次提交
-
-
由 Mark VanderVoord 提交于
-
- 07 6月, 2018 1 次提交
-
-
由 Trond Einar Snekvik 提交于
Adds support for :mock_suffix when generating mock setup and teardown functions. Also documents both prefix and suffix in the helper script guide.
-
- 20 11月, 2017 1 次提交
-
-
由 Krzysztof Kwiatkowski 提交于
Auto generated test runner should generate a code which includes setjmp.h only if UNITY_EXCLUDE_SETJMP_H is not defined
-
- 01 11月, 2017 1 次提交
-
-
由 John Lindgren 提交于
-
- 09 10月, 2017 2 次提交
-
-
由 John Lindgren 提交于
- Enable support for Green Hills Software compiler - Define weak implementations only once except on Windows
-
由 John Lindgren 提交于
MinGW supports a limited form of weak symbols, with the restriction that weak/default implementations need to be defined in the same translation unit they are called from. Strong/overriding symbols may of course be specified in a different translation unit.
-
- 14 9月, 2017 1 次提交
-
-
由 John Lindgren 提交于
This is simpler and more flexible than embedding C code in the Ruby options (:suite_setup and :suite_teardown). However, support for :suite_setup and :suite_teardown is kept for backwards compatibility. Several configurations are possible: 1. :suite_setup and :suite_teardown options provided and used. 2. :suite_setup and :suite_teardown options not provided (nil): 2a. Weak symbols not supported; suiteSetUp() and suiteTearDown() are not called. It would be simpler to make user-provided functions mandatory in this case, but it could break some pre-existing test suites. 2b. Weak symbols are supported and the stub implementations of suiteSetUp() and suiteTearDown() are called if there are no user-provided functions. 2c. Weak symbols are supported but overridden by user-provided suiteSetUp() and suiteTearDown() functions.
-
- 12 9月, 2017 1 次提交
-
-
由 Mark VanderVoord 提交于
-
- 29 3月, 2017 1 次提交
-
-
由 Mark VanderVoord 提交于
-
- 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.
-
- 21 3月, 2017 3 次提交
-
-
由 Mark VanderVoord 提交于
-
由 Mark VanderVoord 提交于
-
由 Mark VanderVoord 提交于
-
- 14 3月, 2017 2 次提交
-
-
由 Mark VanderVoord 提交于
-
由 Mark VanderVoord 提交于
-
- 25 12月, 2016 1 次提交
-
-
由 jsalling 提交于
-
- 10 11月, 2016 1 次提交
-
-
由 Mark VanderVoord 提交于
Added ability to inject defines, much like what was built into Ceedling before Ceedling switched to just using this generator.
-
- 22 9月, 2016 2 次提交
-
-
由 L.J. Hill 提交于
-
由 L.J. Hill 提交于
This fixes #220. Removing strings from test files is still dangerous, but much less likely to cause problems after this change to do the removal after removing comments. The bug could still manifest if a test file contains defines two macros, one that contains a single quotation mark and then another defined somewhere after it that contains a single quotation mark. Everything in between the aforementioned quotation marks would still be ignored after this commit, but that is an unlikely scenario.
-
- 13 7月, 2016 1 次提交
-
-
由 Daniel Murdin 提交于
Change-Id: I2dbae30e21ab31921817f68fd7a5e08d21c76626
-
- 09 7月, 2016 1 次提交
-
-
由 Mark VanderVoord 提交于
-
- 27 6月, 2016 1 次提交
-
-
由 Mark VanderVoord 提交于
-
- 23 6月, 2016 1 次提交
-
-
由 Mark VanderVoord 提交于
Updated method of testing generate_test_runner script to be a FUNCTIONAL test instead of a perfect code match. Backfilled most tests and added some coverage not previously present. Still need to test new command line args and a few cmock details.
-
- 22 6月, 2016 1 次提交
-
-
由 Mark VanderVoord 提交于
Script verification hasn't been added yet.
-
- 15 5月, 2016 1 次提交
-
-
由 Andrzej Bieniek 提交于
-
- 26 2月, 2016 1 次提交
-
-
由 Mark VanderVoord 提交于
-
- 02 2月, 2016 1 次提交
-
-
由 Peter Mendham 提交于
feedback from @mvandervoord (Thanks).
-
- 29 1月, 2016 1 次提交
-
-
由 Peter Mendham 提交于
This supports mock headers of the form: #include "some/dir/MockMyCode.h" Where the mock name is actually MockMyCode. I *think* this is the most common scenario when working with mocks in subdirectories but if not this could be modified to support alternate schemes.
-
- 27 1月, 2016 1 次提交
-
-
由 Peter Mendham 提交于
-
- 20 1月, 2016 2 次提交
-
-
由 Peter Mendham 提交于
Changed the guard syntax as it was cumbersome for header files in deep sub-directories. Added framework/mock includes to make the header file stand alone. Made sure that a valid prototype was generated in the case of no arguments (void).
-
由 Peter Mendham 提交于
This allows alternative entry points. This is intended for the integration of the unit test into a larger system or for it to be used with a platform/OS which requires an application entry point other than main. At the moment there is no way to change the type signature.
-
- 08 1月, 2016 1 次提交
-
-
由 Mark VanderVoord 提交于
-
- 11 12月, 2015 1 次提交
-
-
由 Mark VanderVoord 提交于
- Fixed a big ugly error in the fancy RUN_TEST handler
-
- 18 8月, 2015 2 次提交
-
-
由 Mark VanderVoord 提交于
-
由 Mark VanderVoord 提交于
Output used headers from test runner generator
-
- 22 7月, 2015 1 次提交
-
-
由 Mark VanderVoord 提交于
the test runner generator now has the ability to also output a header file for the tests, which can get pulled into the test itself if desired.
-
- 21 7月, 2015 1 次提交
-
-
由 Mark VanderVoord 提交于
protect against capturing both declaration and definitions and therefore creating a runner which runs that test twice.
-