Drew Fisher wrote: > Vladimir, > > run_test assumes there is a file in $TET_SUITE_ROOT/<suite > name>/config/test_config > > If you put a file there with that name, you'll be able to simply run: > > run_test <suite name> <test case> without using the -F flag to pass a > configuration file in.
Thanks a lot, this works nicely. However, upon close inspection I have realized that the test purpose was not run properly with TET_OUTPUT_CAPTURE=True and at the same time I am printing to stdout+stderr (regardless if in the test purpose itself or elsewhere). Basically, the journal contains only the stdout/stderr messages but not those printed via tet_infoline(): 15|0 3.7-lite 1|TCM Start (auto-generated by TCC) 400|0 1 1 12:40:02|IC Start (auto-generated by TCC) 200|0 1 12:40:02|TP Start (auto-generated by TCC) 100|0|XXX stdout 100|0|XXX stderr 220|0 1 0 12:40:03|PASS (auto-generated by TCC) 410|0 1 1 12:40:03|IC End (auto-generated by TCC) 80|0 0 12:40:03|TC End, scenario ref 1-0 900|12:40:03|TCC End And the summary then contains the following: PASS : 0 FAIL : 0 UNRESOLVED : 0 UNINITIATED : 0 OTHER : 1 The 'auto-generated by TCC' message is probably the key but I am stuck since my knowledge about inner workings of TET is very limited. v.
