mobiusloop 0.1.3 → 0.1.5

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (52) hide show
  1. checksums.yaml +4 -4
  2. data/Gemfile +2 -2
  3. data/README.md +179 -117
  4. data/bin/a2h +17 -0
  5. data/bin/bcat +17 -0
  6. data/bin/btee +17 -0
  7. data/bin/coderay +17 -0
  8. data/bin/coveralls +17 -0
  9. data/bin/htmldiff +17 -0
  10. data/bin/kramdown +17 -0
  11. data/bin/ldiff +17 -0
  12. data/bin/{mobiusloop → mobius} +0 -0
  13. data/bin/nokogiri +17 -0
  14. data/bin/pry +17 -0
  15. data/bin/rackup +17 -0
  16. data/bin/rake +17 -0
  17. data/bin/rspec +17 -0
  18. data/bin/term_cdiff +17 -0
  19. data/bin/term_colortab +17 -0
  20. data/bin/term_decolor +17 -0
  21. data/bin/term_display +17 -0
  22. data/bin/term_mandel +17 -0
  23. data/bin/thor +17 -0
  24. data/bin/tilt +17 -0
  25. data/bin/yard +17 -0
  26. data/bin/yardoc +17 -0
  27. data/bin/yri +17 -0
  28. data/build +7 -0
  29. data/docs/Outcome_Options.docx +0 -0
  30. data/examples/mobiusloop/increase_readers.goal +6 -8
  31. data/gherkin-languages.json +6 -3
  32. data/lib/cucumber/cli/main.rb +1 -1
  33. data/lib/cucumber/project_initializer.rb +11 -6
  34. data/lib/mobiusloop/config/config.yml +9 -0
  35. data/lib/mobiusloop/config/config_file.rb +20 -0
  36. data/lib/mobiusloop/hooks.rb +22 -0
  37. data/lib/mobiusloop/mobius_steps.rb +7 -5
  38. data/lib/mobiusloop/objective.rb +67 -1
  39. data/lib/mobiusloop/outcome.rb +68 -12
  40. data/lib/mobiusloop/scale.rb +3 -16
  41. data/lib/mobiusloop/version +1 -0
  42. data/mobiusloop.gemspec +17 -15
  43. data/mobiusloop.gemspec.lock +10 -0
  44. data/spec/mobiusloop/measure_spec.rb +17 -0
  45. data/spec/mobiusloop/objective_spec.rb +52 -0
  46. data/spec/mobiusloop/outcome_spec.rb +59 -0
  47. data/spec/mobiusloop/page_response_scale_spec.rb +16 -0
  48. data/spec/mobiusloop/scale_error.rb +16 -0
  49. data/spec/mobiusloop/scale_sample.rb +18 -0
  50. data/spec/mobiusloop/scale_spec.rb +23 -0
  51. metadata +183 -25
  52. data/CONTRIBUTING.md +0 -68
@@ -1,68 +0,0 @@
1
- ## About to create a new Github Issue?
2
-
3
- We appreciate that. But before you do, please learn our basic rules:
4
-
5
- * This is not a support forum. If you have a question, please go to [The Cukes Google Group](http://groups.google.com/group/cukes).
6
- * Do you have an idea for a new feature? Then don't expect it to be implemented unless you or someone else sends a [pull request](https://help.github.com/articles/using-pull-requests). You might be better to start a discussion on [the google group](http://groups.google.com/group/cukes).
7
- * Reporting a bug? Please tell us:
8
- * which version of Cucumber you're using
9
- * which version of Ruby you're using.
10
- * How to reproduce it. Bugs with a failing test in a [pull request](https://help.github.com/articles/using-pull-requests) get fixed much quicker. Some bugs may never be fixed.
11
- * Want to paste some code or output? Put \`\`\` on a line above and below your code/output. See [GFM](https://help.github.com/articles/github-flavored-markdown)'s *Fenced Code Blocks* for details.
12
- * We love [pull requests](https://help.github.com/articles/using-pull-requests). But if you don't have a test to go with it we probably won't merge it.
13
-
14
- # Contributing to Cucumber
15
-
16
- The rest of this document is a guide for those maintaining Cucumber, and others who would like to submit patches.
17
-
18
- ## Talking with other devs
19
-
20
- You can chat with the core team on https://gitter.im/cucumber/cucumber. We try to have office hours on Fridays.
21
-
22
- ## Note on Patches/Pull Requests
23
-
24
- * Fork the project. Make a branch for your change.
25
- * Make your feature addition or bug fix.
26
- * Make sure your patch is well covered by tests. We don't accept changes to Cucumber that aren't tested.
27
- * Please do not change the Rakefile, version, or history.
28
- (if you want to have your own version, that is fine but
29
- bump version in a commit by itself so we can ignore when we merge your change)
30
- * Send us a pull request.
31
-
32
- ## Running tests
33
-
34
- gem install bundler
35
- bundle install
36
- bundle exec rake
37
-
38
- To get code coverage results, run `bundle exec rake cov`
39
-
40
- ## Release Process
41
-
42
- * Bump the version number in `lib/cucumber/platform.rb`.
43
- * Make sure `History.md` is updated with the upcoming version number, and has entries for all fixes.
44
- * No need to add a `History.md` header at this point - this should be done when a new change is made, later.
45
- * Make sure you have up-to-date and clean copy of cucumber/cucumber.github.com.git at the same level as cucumber repo.
46
-
47
- Now release it
48
-
49
- bundle update
50
- bundle exec rake
51
- git commit -m "Release X.Y.Z"
52
- rake release
53
-
54
- ## Gaining Release Karma
55
-
56
- To become a release manager, create a pull request adding your name to the list below, and include your Rubygems email address in the ticket. One of the existing Release managers will then add you.
57
-
58
- Current release managers:
59
- * [Matt Wynne](https://rubygems.org/profiles/mattwynne)
60
- * [Aslak Hellesøy](https://rubygems.org/profiles/aslakhellesoy)
61
- * [Oleg Sukhodolsky](https://rubygems.org/profiles/os97673)
62
- * [Steve Tooke](https://rubygems.org/profiles/tooky)
63
- * [Björn Rasmusson](https://rubygems.org/profiles/brasmusson)
64
-
65
- To grant release karma, issue the following commands:
66
-
67
- gem owner cucumber --add <NEW OWNER RUBYGEMS EMAIL>
68
- gem owner cucumber-core --add <NEW OWNER RUBYGEMS EMAIL>