Bram writes: > At the moment foo() returns 3. > > Time passes and code changes. > > Now there are 3 options: > > foo() returns 1, this will result in 'unexpected todo test passed' > being outputted; > foo() returns 3, no special output is produced; > foo() returns 4, no special output is produced; > > To me the last one seems like a limitation. > The result of foo() is now different then when the TODO test was > written but there is nothing in the output that indicates this.
If you believe that (until the TODO is done) foo will consistently return 3, and you wish to be alerted if it suddenly starts returning 4, then surely you can do that with a non-TODO test which checks for its being 3? Then, when the TODO is done you can remove that test entirely (while also removing the TODO marker from the check for 1)? Smylers
