Menu

Adding CUnit Testing to an Existing Project

Help
brainsick
2008-08-08
2012-10-25
  • brainsick

    brainsick - 2008-08-08

    Is there a recommended directory structure or naming standard for incorporating CUnit Testing into a project? For example, say I have:

    project/ChangeLog
    project/configure
    project/COPYING
    project/Makefile
    project/README
    project/src/Makefile
    project/src/program.c
    project/src/program.h
    project/src/thing.c
    project/src/thing.h
    project/TODO

    Where would you put the CUnit tests that you create? Do they go into the src/ directory or should a new test/ directory be created at the project level? Do the tests go into the src/ directory with a <file>_test.c naming standard?

    I'm just looking for some "best practices" kind of guidance. If I'm going to add CUnit testing to a project, I'd like to do it in the most common or accepted fashion.

     
    • brainsick

      brainsick - 2008-08-08

      If anyone knows of some projects using CUnit testing, please post links. I'd like to check out the repositories.

       

Log in to post a comment.