-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
repypp.py
should have unit tests
#161
Comments
@XuefengHuang suggested we also test calling I'll also add that we should test lines like |
I have added some unit tests to check different situations as the issue describes. This is my PR(#163). |
I have tested this on linux - ubuntu and below are the test cases that pass: -rw-rw-r-- 1 cib cib 878 May 15 22:07 ut_seattlelibv2_repypp_samearguments.py Below is the test case that fail:- cib@cib-VirtualBox:~/xeufeng/seattlelib_v2/RUNNABLE$ python utf.py -f ut_seattlelibv2_repypp_specialcomments.py Running: ut_seattlelibv2_repypp_specialcomments.py [ FAIL ]Standard out : ..............................Expected.............................. Noneand test case leaves and trace of file that i think can be removed by os.remove, below is the file: -rw-rw-r-- 1 cib cib 86 May 15 22:11 testfile_repypp_example3.repy |
repypp.py
, the Repy preprocessor, does not have unit tests. This makes testing parts of the build scripts in SeattleTestbed/common difficult.Things we should probably test:
#include
statements#include
statements:(We will want to have realistic-looking Repy programs and realistic-looking libraries to
#include
for these purposes).The text was updated successfully, but these errors were encountered: