Add beginnings of TODO.
catseye
12 years ago
0 | TODO | |
1 | ==== | |
2 | ||
3 | (collected from the [Falderal issue tracker on Bitbucket][] and the | |
4 | [py-falderal issue tracker on github][]) | |
5 | ||
6 | Falderal Literate Test Format | |
7 | ----------------------------- | |
8 | ||
9 | ### Allow use of patterns in expected output | |
10 | ||
11 | 2011-05-17 | |
12 | ||
13 | Likely by way of regexps. This would be particularly valuable in | |
14 | exception-expecting tests, where we don't care about details such as the | |
15 | line number of the Haskell file at which the exception occurred. | |
16 | ||
17 | ### Allow equivalency tests to be defined and run. | |
18 | ||
19 | 2011-05-17 | |
20 | ||
21 | To test functions of type `(Eq a) => String -> a`, you should be able to | |
22 | give give multiple input strings in a set; if the function does not map | |
23 | them all to the same value, that's a test failure. | |
24 | ||
25 | Syntax for an equivalency test might look like this: | |
26 | ||
27 | | 2+2 | |
28 | == | |
29 | | 3+1 | |
30 | == | |
31 | | 7-3 | |
32 | ||
33 | ||
34 | Test.Falderal | |
35 | ------------- | |
36 | ||
37 | ### Show filenames and implementations in standard failure report ### | |
38 | ||
39 | 2011-12-11 | |
40 | ||
41 | To make the standard failure report more useful, it should show the source | |
42 | Falderal document filename(s) in the summary, the relevant source filename | |
43 | in each error, and the implementation used to test the functionality in | |
44 | each error. | |
45 | ||
46 | ### Flag invalid sequences of lines as errors ### | |
47 | ||
48 | 2011-08-05 | |
49 | ||
50 | Currently, in `convertLinesToBlocks`, some invalid sequences of lines are | |
51 | ignored. They should be flagged as errors in the test suite file. |