Mark VanderVoord d4197dacd0 There was no reason that CMock init and destroy calls should be in the protected blocks. teardown is more flexible if verify is called afterwards.

2014-04-21 16:55:12 -04:00

..

testsample_cmd.c

Fixed initialization of data structure by just doing it manually instead of statically (goodbye compiler warnings!)

2014-03-07 15:17:25 -05:00

testsample_def.c

Fixed initialization of data structure by just doing it manually instead of statically (goodbye compiler warnings!)

2014-03-07 15:17:25 -05:00

testsample_mock_cmd.c

There was no reason that CMock init and destroy calls should be in the protected blocks. teardown is more flexible if verify is called afterwards.

2014-04-21 16:55:12 -04:00

testsample_mock_def.c

There was no reason that CMock init and destroy calls should be in the protected blocks. teardown is more flexible if verify is called afterwards.

2014-04-21 16:55:12 -04:00

testsample_mock_new1.c

There was no reason that CMock init and destroy calls should be in the protected blocks. teardown is more flexible if verify is called afterwards.

2014-04-21 16:55:12 -04:00

testsample_mock_new2.c

There was no reason that CMock init and destroy calls should be in the protected blocks. teardown is more flexible if verify is called afterwards.

2014-04-21 16:55:12 -04:00

testsample_mock_param.c

There was no reason that CMock init and destroy calls should be in the protected blocks. teardown is more flexible if verify is called afterwards.

2014-04-21 16:55:12 -04:00

testsample_mock_run1.c

There was no reason that CMock init and destroy calls should be in the protected blocks. teardown is more flexible if verify is called afterwards.

2014-04-21 16:55:12 -04:00

testsample_mock_run2.c

There was no reason that CMock init and destroy calls should be in the protected blocks. teardown is more flexible if verify is called afterwards.

2014-04-21 16:55:12 -04:00

testsample_mock_yaml.c

There was no reason that CMock init and destroy calls should be in the protected blocks. teardown is more flexible if verify is called afterwards.

2014-04-21 16:55:12 -04:00

testsample_new1.c

Fixed initialization of data structure by just doing it manually instead of statically (goodbye compiler warnings!)

2014-03-07 15:17:25 -05:00

testsample_new2.c

Fixed initialization of data structure by just doing it manually instead of statically (goodbye compiler warnings!)

2014-03-07 15:17:25 -05:00

testsample_param.c

Fixed initialization of data structure by just doing it manually instead of statically (goodbye compiler warnings!)

2014-03-07 15:17:25 -05:00

testsample_run1.c

Fixed initialization of data structure by just doing it manually instead of statically (goodbye compiler warnings!)

2014-03-07 15:17:25 -05:00

testsample_run2.c

Fixed initialization of data structure by just doing it manually instead of statically (goodbye compiler warnings!)

2014-03-07 15:17:25 -05:00

testsample_yaml.c

Fixed initialization of data structure by just doing it manually instead of statically (goodbye compiler warnings!)

2014-03-07 15:17:25 -05:00