joewalnes / tinytest

A tiny unit-testing framework for C

TinyTest

A really really really tiny and simple no-hassle C unit-testing framework.

Features

• No library dependencies. Not even itself. Just a header file.
• Simple ANSI C. Should work with virtually every C or C++ compiler on virtually any platform.
• Reports assertion failures, including expressions and line numbers.
• Stops test on first failed assertion.
• ANSI color output for maximum visibility.
• Easy to embed in apps for runtime tests (e.g. environment tests).

Example Usage

#include "tinytest.h"
#include "mylib.h"

void test_sheep()
{
  ASSERT("Sheep are cool", are_sheep_cool());
  ASSERT_EQUALS(4, sheep.legs);
}

void test_cheese()
{
  ASSERT("Cheese is tangy", cheese.tanginess > 0);
  ASSERT_STRING_EQUALS("Wensleydale", cheese.name);
}

int main()
{
  RUN(test_sheep);
  RUN(test_cheese);
  return TEST_REPORT();
}

To run the tests, compile the tests as a binary and run it.

2010-2014, -Joe Walnes [email protected] http://joewalnes.com

tinytest's Issues

License information

Hi,

Is there any license information for this project? I'd like to use it in some of my own code which is Apache 2.0 and another which is 2-clause BSD, but I prefer if all code I reuse is easily attributable and licensed under agreeable terms; without that, technically I don't have the legal permission to use it at all!

(I'm not being pushy, but obviously something really liberal would be great!)

This is not how C works

By having variables and code in a header file, every time that header is included in a different file, a separate function and variable is created. No one should touch this library as is unless they want to stare at endless linker issues and broken code.

fdgdfgdkjh

kjkj

string.h

I had not included <string.h> but used ASSERT_STRING_EQUALS. So I had an error because strcmp isn't defined.
It is not really important but including <string.h> in the header makes sense.
Thank you for sharing this piece of code.

kjh

kjh