How throwtheswitch/ceedling works
Project type and purpose
• This is “Ceedling,” a Ruby-based, command-line build and unit-test automation tool for C projects. It orchestrates compilation, test suite builds (via Unity, CMock, CException), plugin loading, and reporting.
File structure
• Top‐level “bin/” holds the CLI executables (ceedling, rake tasks, wrappers).
• “lib/ceedling/” contains the core application code: configurator, task invoker, generator, runner, plugin manager, utilities (file system, path, YAML wrappers), report generators, etc.
• “plugins/” holds subdirectories for each plugin; each plugin has its own lib, config, Rakefile, assets, and examples.
• “spec/” has the RSpec suite that tests the Ruby core.
• “examples/” and “assets/” provide sample C projects and config files.
• “docs/” holds user-manual, API guides, plugin development guides, and release notes.
• Configuration files: project.yml in assets and examples, .rubocop.yml, .gitignore, Gemfile/Gemfile.lock, ceedling.gemspec, Rakefile.
README for additional insights
• Describes the three integrated C frameworks (Unity, CMock, CException) and plugin support.
• Highlights command-line entry (“ceedling test:all”), project configuration (YAML), plugin architecture, Docker images, and Rake-based self-tests.
Detail and coverage
• Every layer: entrypoint, configuration, plugin loading, build pipeline, test execution, reporting.
• Examples and spec suites as consumers of the core engine (but not part of the production build path).