Sha256: 4faf34962bfde1801679493471e5d06bb8d814443ca1bbb47e54397f8639a88b

Contents?: true

Size: 1.3 KB

Versions: 1

Compression:

Stored size: 1.3 KB

Contents

MMF 0.4
  - show exceptions
  - show code snippets
MMF 0.5
  - show incomplete suite
  - show undefined Scenarios/suite
  - show undefined Steps
  - show incomplete wrap-up for steps/scenarios
  - show incomplete running time
MMF 0.6
  - deal with Scenario Examples
MMF 1.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

- 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)

Version data entries

1 entries across 1 versions & 1 rubygems

Version Path
cuukie-0.1.3 doc/backlog.txt