Ceedling
Ceedling copied to clipboard
ThrowTheSwitch
Ruby-based unit testing and build system for C projects
If you add "gcov:all" as default task, it compiles the relevant files with coverage, but no coverage report is created. ``` # tweak the way ceedling handles automatic tasks :build_root:...
We're seeing Ceedling return exit code 0 even though there are failing tests with `ceedling test:all`: ``` ----------------------- 14 Tests 4 Failures 0 Ignored FAIL Ceedling operations completed in 2.56...
Hi, using latest Ceedling gem downloaded from your GH release artifacts. I have a big monorepo managed by rake that I am trying to integrate with ceedling for all the...
After following the install steps in the github workflow, I am running 'rake ci' on the latest release of Ceedling but 26/255 tests are failing. Any ideas why?
Version 1.x currently builds each file for each test (ex: a file `blah.c` is compiled for each test that includes `blah.c`). Before this, we had the ability to only compile...
- Each report plugin should notify ceedling if it plans to write to stdout, stderr, etc - (perhaps a retval? perhaps a callback? perhaps a variable?) - If multiple reports...
I strongly suspect this only happens when files are included in both tests and source lists?
Then it doesn't get removed from all required places. A possible solution might be to have the build step pull from both source and test lists... and NOT merge tests...
  The source code is not in the ceedling project directory. The test execution was successful, and the coverage report output was 0! How can I set it up...
Metadata
Owner
Metadata
Ruby-based unit testing and build system for C projects