This serves as a good starting point for testing and semi-automatization purposes for LV 706.007.
- fork your own copy from https://gist.github.com/2012324
git clone <that copy's private clone URL> framework
side-by-side with your normal repository so you will end up with two directoriesuni/sep/project/
anduni/sep/framework/
cd framework; git submodule init; git submodule update
- create a symlink from
uni/sep/framework/src/
touni/sep/project/<src>
-<src>
is where your.cpp
and.h
files lie, in your private repository (subversion or git) that noone will see.
make
- just compile the program
make tests
- compile the program if necessary, then run the tests on it
make deliverable
- create archive (ready for abgabe, DO NOT FORGET to update the
DELIVERABLES
variable in Makefile) - run the tests beforehand => IMPOSSIBLE to hand in something that doesn't pass the tests
- create archive (ready for abgabe, DO NOT FORGET to update the
make format
- run astyle over the source code (the
DELIVERABLES
variable) - not guaranteed to be perfect, but Weber-proof in the scope ofastyle
at least
- run astyle over the source code (the
Add your tests in uni/sep/framework/tests/
. The documentation is at http://cxxtest.com/cxxtest/doc/guide.html.
Commit and push your tests, so anyone can benefit from them.
- fun
- profit (ECTS)