![]() ![]() Ceedling will search it out and compile it into your test. Every include file in the test_xxx.c file is assumed to have a corresponding translation unit (.c file) with the same base name. There is other learning curve stuff like ceedling test_xxx.c files are sort of magic in that they contain your tests but also act like a linker control file. This can be challenging on some project structures but if all else fails you just put ever folder by name in your project.yml file (not best but ultimate fallback for crazy messed up projects) If you are adapting to a new project you will need to fiddle around with the project.yml file to tell ceedling where your source files and include files are, and where you want your test files to go. Under Linux Ceedling is super easy to setup and run. ![]() ![]() Mostly notes to myself on getting Ruby and GCC on windows. I have a personal GIST on setting up under older Windows here. Grenning's Test Driven Development for Embedded C (Pragmatic Programmers). The best book on this subject (not perfect but still darn good) is James W. You can run ceedling generated tests on a target but you probable don't want to. You typically test your code on your PC using a standards based compiler of some sort, not necessarily your cross compiler for your embedded system. The first thing you should understand is that first and foremost Ceedling or any unit test framework is intended to test your code and by extension your ultimate project. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |