crab 0.1.0 → 0.1.1

Sign up to get free protection for your applications and to get access to all the features.
Files changed (4) hide show
  1. data/.gitignore +1 -0
  2. data/README.md +135 -0
  3. data/lib/crab/version.rb +1 -1
  4. metadata +4 -3
data/.gitignore CHANGED
@@ -5,3 +5,4 @@ pkg/*
5
5
  tmp
6
6
  .rally_credentials
7
7
  tags
8
+ .rally_project
@@ -0,0 +1,135 @@
1
+ crab: A Cucumber-Rally bridge
2
+ =============================
3
+
4
+ `crab` bridges the gap between stories specified, managed and tracked in
5
+ [Rally][1] and stories that are described and run as automated acceptance
6
+ and functional tests through [Cucumber][2].
7
+
8
+ It aims to provide seamless integration between both tools, allowing
9
+ people to communicate across these without much effort while trying to
10
+ stay out of the way as much as possible.
11
+
12
+ [1]: http://www.rallydev.com
13
+ [2]: http://cukes.info
14
+
15
+ Installing
16
+ ----------
17
+
18
+ `crab` is distributed as a Ruby Gem. To install it, simply issue:
19
+
20
+ gem install crab
21
+
22
+ And you should be good to go. To make sure everything is ok, try:
23
+
24
+ crab -h
25
+
26
+ If you see a help message, everything went fine.
27
+
28
+ Usage
29
+ -----
30
+
31
+ As `crab` is still in its infancy, it doesn't support very complex
32
+ workflows, but does the job for the author and his team so far.
33
+
34
+ The team wrote a few stories directly in Rally before deciding that
35
+ writing them straight in Cucumber features would be better suited.
36
+ Initially, there were concerns around migration of the existing data.
37
+ Thankfully, that part is easy:
38
+
39
+ # crab login -u cv@lixo.org -p mypassword
40
+ Logged in as cv@lixo.org.
41
+
42
+ # crab project "World Domination 3000"
43
+ # crab list
44
+ US1001: Arms Rockets Upon Successful Boot
45
+ US1002: Launches Rockets Upon Command from Evil Mastermind
46
+ US1003: Transfer $0.01 From All Bank Accounts
47
+ ...
48
+
49
+ # crab find Rockets
50
+ US1001: Arms Rockets Upon Successful Boot
51
+ US1002: Launches Rockets Upon Command from Evil Mastermind
52
+
53
+ # crab show US1001
54
+ Feature: [US1001] Arms Rockets After Boot
55
+
56
+ In order to gain bargaining power with Super Hero
57
+ As an Evil Mastermind
58
+ Wants visible evidence that the rockets have been armed
59
+
60
+ ...
61
+
62
+ If there are any test cases, their steps get converted into Cucumber
63
+ steps:
64
+
65
+ # crab show US1001
66
+ ...
67
+
68
+ Scenario: [TC10001] Rocket Silo Is Unlocked
69
+ Given a silo where the rockets are stored
70
+ When I boot the system
71
+ The hatches should unlock
72
+
73
+ ...
74
+
75
+ Some data about stories can also be edited straight from the command line.
76
+ In that sense, `crab` acts more like a CLI interface to Rally than a bridge
77
+ between Rally and Cucumber, but the team thought these were *very* convenient
78
+ features to have:
79
+
80
+ # crab update US1001 --name "Arms Rockets Upon Successful Boot" --state completed
81
+
82
+ There are more switches. Check out `crab update --help` to find out more.
83
+
84
+ To do
85
+ -----
86
+
87
+ - Add a `push` subcommand which parses a Cucumber feature and adds or updates it in Rally
88
+ - Add a way to create, edit and delete test cases / scenarios from the command line
89
+ - `pull` is not very smart and could detect feature files being moved from one dir to another
90
+ - Recursively look for a `.rally_project` file like Git does with `.git` dirs
91
+ - Encrypt password in generated `~/.rally_credentials`
92
+ - Verbose logging (especially before any change or destructive operations in Rally)
93
+ - Dry-run mode
94
+ - Figure out how to stub or simulate Rally (tests are taking way too long already)
95
+
96
+ Suggestions? Please get in touch!
97
+
98
+ Authors and Contributors
99
+ ------------------------
100
+
101
+ Carlos Villela <cvillela@thoughtworks.com>
102
+ Rodrigo Kochenburger <rkochen@thoughtworks.com>
103
+ Fabio Rehm <frehm@thoughtworks.com>
104
+
105
+ And last but not least, Rodrigo Spohr <rspohr@thoughtworks.com> for the user testing.
106
+
107
+ Disclaimers
108
+ -----------
109
+
110
+ This project and its authors have no affiliation with Rally Software Development Corp. or the Cucumber project.
111
+
112
+ It was written as necessity in a real-world project, and by no means should represent endorsement of either product.
113
+
114
+ Rally (c) 2003-2011 Rally Software Development Corp.
115
+
116
+ Cucumber (c) 2008-2011 Aslak Hellesøy et al.
117
+
118
+ License
119
+ -------
120
+
121
+ Copyright 2011 Carlos Villela <cvillela@thoughtworks.com>
122
+
123
+ Licensed under the Apache License, Version 2.0 (the "License");
124
+ you may not use this file except in compliance with the License.
125
+ You may obtain a copy of the License at
126
+
127
+ http://www.apache.org/licenses/LICENSE-2.0
128
+
129
+ Unless required by applicable law or agreed to in writing, software
130
+ distributed under the License is distributed on an "AS IS" BASIS,
131
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express
132
+ or implied. See the License for the specific language governing
133
+ permissions and limitations under the License.
134
+
135
+
@@ -1,3 +1,3 @@
1
1
  module Crab
2
- VERSION = "0.1.0"
2
+ VERSION = "0.1.1"
3
3
  end
metadata CHANGED
@@ -1,13 +1,13 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: crab
3
3
  version: !ruby/object:Gem::Version
4
- hash: 27
4
+ hash: 25
5
5
  prerelease:
6
6
  segments:
7
7
  - 0
8
8
  - 1
9
- - 0
10
- version: 0.1.0
9
+ - 1
10
+ version: 0.1.1
11
11
  platform: ruby
12
12
  authors:
13
13
  - Carlos Villela
@@ -157,6 +157,7 @@ files:
157
157
  - .gitignore
158
158
  - .rvmrc
159
159
  - Gemfile
160
+ - README.md
160
161
  - Rakefile
161
162
  - bin/crab
162
163
  - crab.gemspec