You can clone with
HTTPS or Subversion.
Document the named subject feature.
Update feature cuke with RSpec code style.
- Apply Rubocop code style to the example specs
- Update the scenario names to read more as feature descriptions
Use code backticks in feature and scenario names.
Standardize on `RSpec.describe` over `describe`.
Standardize capitalization of scenarios.
When viewing in Relish, scenarios read as section titles. General
punctuation dictates that section titles should start capitalized.
Add `is_expected` for expect-based one-liner syntax.
Update cukes to new syntax
Added spec and yard docs for #subject! method, and improved cuke exam…
Added `subject!` method for invoking subject in a before block like `…
Identify ruby code for syntax highlighting
Thanks to @charlietanksley, @alindeman, and @greggroth for the regex
help. Fixes #708
add note that explicit ref to subject is not recommended
upgrade cucumber and aruba
more cuke tweaks
add rspec examples for previous commit
Fix issue when RSpec invokes the subject block multiple times
- Closes #244.
update some features
tweak subject features
update to aruba 0.1.9
update features to run in ruby-1.9.2
one less wip feature
Evaluate explicit subject block in instance context
Add -rrubygems to the generated autotest command if defined?(:Gem)
convert features to aruba
add load paths and requires to cuke env
Ported subject functionality from RSpec 1.2.X