...this is something I should have done since YEARS, really... Whenever working with symbolically represented data, tests typically involve checking *hundreds* of expected results, and thus it can be really hard to find out where the failure actually happens; it is better for readability to have the expected result string immediately in the test code; now this expected result can be marked with a user-defined literal, and then on mismatch the expected and the real value will be printed. |
||
|---|---|---|
| .. | ||
| common | ||
| include | ||
| lib | ||
| lumiera | ||
| plugin | ||
| stage | ||
| steam | ||
| tool | ||
| vault | ||
| .gitignore | ||
| DIR_INFO | ||
| doxygen.dox | ||
| SConscript | ||