How-To

These guides walk through common needs step by step. Each one lists requirements and provides complete examples. The User Manual explains every feature and setting they use.

• Start Testing in Your Project

  ---

  Install the extension, open a project, and run its first test. Most projects need no configuration.

• Debug a Test

  ---

  A launch configuration for Linux, macOS, or Windows, so any test runs under the debugger from its debug button.

• Measure Code Coverage

  ---

  A code coverage plugin mixin with Gcovr, ReportGenerator, or Bullseye, so Run with Coverage shows each line’s hits.

• See Compiler Errors in the Editor

  ---

  The gcc preset, or patterns of your own, so build errors appear at their lines and in the Problems panel.

• Work With Several Projects

  ---

  Projects in subdirectories, several projects in one folder, multi-root workspaces, and project files of your own.

• Run the Ceedling You Use

  ---

  Ceedling in a particular shell, through Bundler, vendored in the project, or selected by name.

• Upgrade Ceedling

  ---

  A new Ceedling release, picked up with a refresh, and the old build layout cleaned out.

• Write Parametrized Tests

  ---

  Unity’s TEST_CASE(), TEST_RANGE(), and TEST_MATRIX(), with each case listed and reported apart.

• Find a Crashing Test

  ---

  Ceedling’s :use_backtrace, so a crash reports as a failure at the test that crashed.

• Run Just One Test

  ---

  A single test function, run without the rest of its file, and what Ceedling still builds. A section of the User Manual.