Sha256: 96236b2d5a22905b0078ac74ecdaaead3ac89b54074cc71e5b78dfa99c54b333
Contents?: true
Size: 1.51 KB
Versions: 1
Compression:
Stored size: 1.51 KB
Contents
MMF 0.1.5 - show incomplete suite - show undefined Scenarios/suite - show undefined Steps - show incomplete wrap-up for steps/scenarios - show incomplete running time MMF 0.1.6 - deal with Scenario Examples - open/close steps MMF 1.0.0 - nice graphics - self-updating Steps - self-updating Scenarios - self-updating suite - self-updating scenario wrap-up - self-updating step wrap-up - self-updating running time Then... - show tags - filter by tag - instead of showing scenarios that appear one by one, show the entire suite ASAP, and then proceed to make each scenario red or green (or whatever). this gives an immediate feeling of where you are in the suite. - show status for each table row (table rows have an associated status in Cucumber formatters, and the HTML formatter seems to take advantage of this. Why? And what consequences does this have on the way Scenario status is calculated in Cuukie?) - find better way to manage Scenario/Step status (Cuukie calculates the status of Scenarios with a few ugly ifs and other dirty tricks. Maybe that information is already known to the formatter, and it's just a matter of using the right formatter events?) - check rbx bug (interestingly, Rubynius has a different idea of where a "step" is. it seems to return different lines for steps than other rubies. I removed the line numbers from tests b/c of this, and b/c they made the tests fragile. Try to put back the line numbers, and test under rbx) - test against rbx
Version data entries
1 entries across 1 versions & 1 rubygems
Version | Path |
---|---|
cuukie-0.1.4 | doc/backlog.txt |