Ruby on Rails Sunday, September 28, 2014

In the Command Window, I run the commands:

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.


C:\Windows\system32>cd c:\Ruby200\bin

c:\Ruby200\bin>gem install cucumber
Fetching: multi_test-0.1.1.gem (100%)
Successfully installed multi_test-0.1.1
Fetching: gherkin-2.12.2-x86-mingw32.gem ( 57%)Fetching: gherkin-2.12.2-x86-ming
Fetching: gherkin-2.12.2-x86-mingw32.gem ( 80%)Fetching: gherkin-2.12.2-x86-ming
Fetching: gherkin-2.12.2-x86-mingw32.gem (100%)
Successfully installed gherkin-2.12.2-x86-mingw32
Fetching: diff-lcs-1.2.5.gem (100%)
Successfully installed diff-lcs-1.2.5
Fetching: cucumber-1.3.17.gem (100%)
Successfully installed cucumber-1.3.17
Parsing documentation for multi_test-0.1.1
Installing ri documentation for multi_test-0.1.1
Parsing documentation for gherkin-2.12.2-x86-mingw32
Installing ri documentation for gherkin-2.12.2-x86-mingw32
Parsing documentation for diff-lcs-1.2.5
Installing ri documentation for diff-lcs-1.2.5
Parsing documentation for cucumber-1.3.17
Installing ri documentation for cucumber-1.3.17
Done installing documentation for multi_test, gherkin, diff-lcs, cucumber after
14 seconds
4 gems installed

c:\Ruby200\bin>cucumber --help
*** WARNING: You must use ANSICON 1.31 or higher (https://github.com/adoxa/ansic
on/) to get coloured output on Windows
Usage: cucumber [options] [ [FILE|DIR|URL][:LINE[:LINE]*] ]+

Examples:
cucumber examples/i18n/en/features
cucumber @rerun.txt (See --format rerun)
cucumber examples/i18n/it/features/somma.feature:6:98:113
cucumber -s -i http://rubyurl.com/eeCl

    -r, --require LIBRARY|DIR        Require files before executing the features
. If this
                                     option is not specified, all *.rb files tha
t are
                                     siblings or below the features will be load
ed auto-
                                     matically. Automatic loading is disabled wh
en this
                                     option is specified, and all loading become
s explicit.
                                     Files under directories named "support" are
 always
                                     loaded first.
                                     This option can be specified multiple times
.
        --i18n LANG                  List keywords for in a particular language
                                     Run with "--i18n help" to see all languages

    -f, --format FORMAT              How to format features (Default: pretty). A
vailable formats:
                                       debug       : For developing formatters -
 prints the calls made to the listeners.
                                       html        : Generates a nice looking HT
ML report.
                                       json        : Prints the feature as JSON
                                       json_pretty : Prints the feature as prett
ified JSON
                                       junit       : Generates a report similar
to Ant+JUnit.
                                       pretty      : Prints the feature as is -
in colours.
                                       progress    : Prints one character per sc
enario.
                                       rerun       : Prints failing files with l
ine numbers.
                                       stepdefs    : Prints All step definitions
 with their locations. Same as
                                                     the usage formatter, except
 that steps are not printed.
                                       usage       : Prints where step definitio
ns are used.
                                                     The slowest step definition
s (with duration) are
                                                     listed first. If --dry-run
is used the duration
                                                     is not shown, and step defi
nitions are sorted by
                                                     filename instead.
                                     Use --format rerun --out features.txt to wr
ite out failing
                                     features. You can rerun them with cucumber
@rerun.txt.
                                     FORMAT can also be the fully qualified clas
s name of
                                     your own custom formatter. If the class isn
't loaded,
                                     Cucumber will attempt to require a file wit
h a relative
                                     file name that is the underscore name of th
e class name.
                                     Example: --format Foo::BarZap -> Cucumber w
ill look for
                                     foo/bar_zap.rb. You can place the file with
 this relative
                                     path underneath your features/support direc
tory or anywhere
                                     on Ruby's LOAD_PATH, for example in a Ruby
gem.
    -o, --out [FILE|DIR]             Write output to a file/directory instead of
 STDOUT. This option
                                     applies to the previously specified --forma
t, or the
                                     default format if no format is specified. C
heck the specific
                                     formatter's docs to see whether to pass a f
ile or a dir.
    -t, --tags TAG_EXPRESSION        Only execute the features or scenarios with
 tags matching TAG_EXPRESSION.
                                     Scenarios inherit tags declared on the Feat
ure level. The simplest
                                     TAG_EXPRESSION is simply a tag. Example: --
tags @dev. When a tag in a tag
                                     expression starts with a ~, this represents
 boolean NOT. Example: --tags ~@dev.
                                     A tag expression can have several tags sepa
rated by a comma, which represents
                                     logical OR. Example: --tags @dev,@wip. The
--tags option can be specified
                                     several times, and this represents logical
AND. Example: --tags @foo,~@bar --tags @zap.
                                     This represents the boolean expression (@fo
o || !@bar) && @zap.

                                     Beware that if you want to use several nega
tive tags to exclude several tags
                                     you have to use logical AND: --tags ~@fixme
 --tags ~@buggy.

                                     Positive tags can be given a threshold to l
imit the number of occurrences.
                                     Example: --tags @qa:3 will fail if there ar
e more than 3 occurrences of the @qa tag.
                                     This can be practical if you are practicing
 Kanban or CONWIP.
    -n, --name NAME                  Only execute the feature elements which mat
ch part of the given name.
                                     If this option is given more than once, it
will match against all the
                                     given names.
    -e, --exclude PATTERN            Don't run feature files or require ruby fil
es matching PATTERN
    -p, --profile PROFILE            Pull commandline arguments from cucumber.ym
l which can be defined as
                                     strings or arrays.  When a 'default' profil
e is defined and no profile
                                     is specified it is always used. (Unless dis
abled, see -P below.)
                                     When feature files are defined in a profile
 and on the command line
                                     then only the ones from the command line ar
e used.
    -P, --no-profile                 Disables all profile loading to avoid using
 the 'default' profile.
    -c, --[no-]color                 Whether or not to use ANSI color in the out
put. Cucumber decides
                                     based on your platform and the output desti
nation if not specified.
    -d, --dry-run                    Invokes formatters without executing the st
eps.
                                     This also omits the loading of your support
/env.rb file if it exists.
    -a, --autoformat DIR             Reformats (pretty prints) feature files and
 write them to DIRECTORY.
                                     Be careful if you choose to overwrite the o
riginals.
                                     Implies --dry-run --format pretty.
    -m, --no-multiline               Don't print multiline strings and tables un
der steps.
    -s, --no-source                  Don't print the file and line of the step d
efinition with the steps.
    -i, --no-snippets                Don't print snippets for pending steps.
    -I, --snippet-type TYPE          Use different snippet type (Default: regexp
). Available types:
                                     classic: Snippets without parentheses. Note
 that these cause a warning from modern versions of Ruby. e.g. Given /^missing s
tep$/
                                     percent: Snippets with percent regexp e.g.
Given %r{^missing step$}
                                     regexp : Snippets with parentheses    e.g.
Given(/^missing step$/)
    -q, --quiet                      Alias for --no-snippets --no-source.
    -b, --backtrace                  Show full backtrace for all errors.
    -S, --strict                     Fail if there are any undefined or pending
steps.
    -w, --wip                        Fail if there are any passing scenarios.
    -v, --verbose                    Show the files and features loaded.
    -g, --guess                      Guess best match for Ambiguous steps.
    -l, --lines LINES                Run given line numbers. Equivalent to FILE:
LINE syntax
    -x, --expand                     Expand Scenario Outline Tables in output.
        --[no-]drb                   Run features against a DRb server. (i.e. wi
th the spork gem)
        --port PORT                  Specify DRb port.  Ignored without --drb
        --dotcucumber DIR            Write metadata to DIR
        --version                    Show version.
    -h, --help                       You're looking at it.

c:\Ruby200\bin>


Please verify if the installation is done correctly or not.

Thank you.

Regards
Rohan Sarker
+913324288069 / +917278539338

--
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-talk+unsubscribe@googlegroups.com.
To post to this group, send email to rubyonrails-talk@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/3a97731b-0c6f-4142-b209-b22ddded925a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

No comments:

Post a Comment