- 09 9月, 2017 1 次提交
-
-
由 Mark VanderVoord 提交于
-
- 26 6月, 2017 1 次提交
-
-
由 Mark VanderVoord 提交于
- Fixed some style issues.
-
- 29 3月, 2017 2 次提交
-
-
由 Mark VanderVoord 提交于
-
由 Mark VanderVoord 提交于
Started to flesh out rubocop settings for this project. Added rakefile tasks to do so. Updated first script to make it compliant.
-
- 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 提交于
-
- 08 2月, 2017 1 次提交
-
-
由 Jeremy Hannon 提交于
unity.h and unity_fixture.h output their results in different string formats. This parseOutput.rb script already parsed the unity.h output to generate a JUnit-style XML summary which could be parsed by CI servers to graph the history of test pass/fail results. The changes in this commit allow the script to also handle the output format of unity_fixture.h which utilizes groups to add a layer of organization for tests. The changes in this commit were authored by Justin Seifi, my coworker, who has approved of me submitting his work back to this open source framework repo.
-
- 31 1月, 2017 1 次提交
-
-
由 Mark VanderVoord 提交于
-
- 25 12月, 2016 1 次提交
-
-
由 jsalling 提交于
-
- 03 12月, 2016 1 次提交
-
-
由 Matt Chernosky 提交于
This resolves #219. When generating a new module, if all the files to generate already exist then it fails as before. If some of the files already exist, then the files that need to be created are created. Any existing files are not changed. Also added a bunch of tests for this feature via rspec. Run them from the test folder with `rake spec`.
-
- 29 11月, 2016 1 次提交
-
-
由 Matt Chernosky 提交于
-
- 23 11月, 2016 1 次提交
-
-
由 Mark VanderVoord 提交于
- configurable case. - better passing of includes and boilerplate information - test only pattern - optional naming conventions for case
-
- 22 11月, 2016 1 次提交
-
-
由 Mark VanderVoord 提交于
-
- 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.
-
- 28 10月, 2016 2 次提交
-
-
由 Mark VanderVoord 提交于
-
由 Mark VanderVoord 提交于
refactor generate_module so that it can be called as a class from within Ceedling (much like the test runner 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.
-
- 21 6月, 2016 2 次提交
-
-
由 Mark VanderVoord 提交于
-
由 Mathias Giacomuzzi 提交于
-
- 18 5月, 2016 1 次提交
-
-
由 Mark VanderVoord 提交于
-
- 15 5月, 2016 1 次提交
-
-
由 Andrzej Bieniek 提交于
-
- 26 2月, 2016 2 次提交
-
-
由 Mark VanderVoord 提交于
-
由 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
-