---
title: "Discussion on \"Compile the C test runner\" | Hashnode"
description: "Discussion on \"Compile the C test runner\". Part 1 of exploring the Unity testing framework to do TDD in C."
url: "https://hashnode.com/posts/compile-the-c-test-runner/6599fd5477b624d3cc32f815"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Compile the C test runner](https://warrenmarkham.hashnode.dev/compile-the-c-test-runner?utm_source=hashnode&utm_medium=feed)

Part 1 of exploring the Unity testing framework to do TDD in C.

Jan 7, 2024 · 6 min read · warrenmarkham.hashnode.dev  
Updated Jan 17, 2024  
Read the article

-   [#test-runner](https://hashnode.com/tag/test-runner)
-   [#tdd](https://hashnode.com/tag/tdd)
-   [#c](https://hashnode.com/tag/c)
-   [#git](https://hashnode.com/tag/git)

## Written by

[Warren Markham](https://hashnode.com/@WarrenMarkham)

@WarrenMarkham · Australia, Melbourne

  
[View profile](https://hashnode.com/@WarrenMarkham)

Committed to Quality

I've worked in an AWS Data Engineer role at Infosys, Australia. Previously, I was a Disability Support Worker. I recently completed a course of study in C and Systems Programming with Holberton School Australia. I'm interested in collaborative workflows and going deeper into TDD, automation and distributed systems.

## Responses 1

Markdown supported · ⌘↵ to post

[Mikalai Kardash](https://hashnode.com/@mkardash)

[Jan 9, 2024](https://hashnode.com/posts/compile-the-c-test-runner/6599fd5477b624d3cc32f815/comment/659d364e822347bbc290f349)

I love how everything unfolds in a series of TDD cycles. Great work! Looking forward to the deep dive about those macros.

[Warren Markham](https://hashnode.com/@WarrenMarkham)

[Jan 9, 2024](https://hashnode.com/posts/compile-the-c-test-runner/6599fd5477b624d3cc32f815/comment/659d364e822347bbc290f349#reply-659dcd4d4e7b11fc231b9ac5)

Thanks for the encouragement! I'm definitely drawn to TDD. I like that it encourages problem-solving techniques that echo processes we might recognise as part of 'doing science':

-   small, controlled steps
-   asking specific questions to get specific answers
-   record keeping
-   controlling variables
-   valuing evidence over guesses
-   documenting knowledge (in tests) so that the outcome can be collaborative and incremental
