Sha256: ca3b14369628445eb9edfecc01cac0e02d5b94d6447f4e6a3ba622ea9f9bdfac

Contents?: true

Size: 1.62 KB

Versions: 1

Compression:

Stored size: 1.62 KB

Contents

MMF 0.2.1
  - better error messages
  - work on any cucumber project out of the box (no need to add require())
MMF 0.2.2
  - deal with Scenario Examples
MMF 0.2.3
  - open/close steps
MMF 0.2.4
  - show incomplete wrap-up for steps/scenarios
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

- default policy for open/close elements (like: close
  successfull scenarios/steps, open unsuccessful ones)
  
- 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.2.0 doc/backlog.txt