Skip to content

Testing Guide

Test file naming in Windows

Test filenames should not include “patch” or “setup”. Test filenames become test executables. Windows Installer Detection Technology (part of UAC) requires administrator privileges to run executables with this naming.

Test Cases & Test Suites

  • How Does a Test Case Even Work?

    A brief overview of how test cases work with simple examples illustrating assertions and mocks.

  • Commented Sample Test File

    A sample test file illustrating the Ceedling conventions that make it go. Includes a discussion of what gets compiled and linked into a test executable.

  • Anatomy of a Test Suite

    How a unit test grows up to become a test suite — what a test executable is, why there are multiple, and Ceedling’s role in building and running them.

Testing with Ceedling

  • Important Conventions & Behaviors

    Much of what Ceedling accomplishes is by convention. Code and file structures and naming trigger sophisticated test build features. Also covers search paths, file extensions, preprocessing, and more.

  • Using Unity, CMock & CException

    Ceedling connects the Unity, CMock, and CException frameworks — each of which can require configuration of its own. Ceedling facilitates this.

  • Partials

    Partials are like a scalpel for your source code. A generated partial allows you to test and mock parts of your code you could not otherwise access without rewriting it first.

  • Build Directive Macros

    In-test macros to accomplish build goals when Ceedling’s conventions aren’t quite enough — adding source files, handling include paths, and more.