Hi Graeme,
Can you tell me how did you do it for cucumber so that i can get some
idea of incorporating the same in watircraft.

Regards,
Pallavi

On Sep 10, 2:53 pm, pallavi shashidhar <pals.sha...@gmail.com> wrote:
> Hi,
> I did update to ci_reporter 1.6.0 and at the command prompt, i give the foll
> command:
> "rake ci:setup:cucumber features" and it gives me the foll errors:
>
> rm -rf features/reports
> c:/ruby/bin/ruby -I "c:/ruby/lib/ruby/gems/1.8/gems/cucumber-0.3.91/lib;lib"
> "c:
> /ruby/lib/ruby/gems/1.8/gems/cucumber-0.3.91/bin/cucumber"  --require
> c:/ruby/li
> b/ruby/gems/1.8/gems/ci_reporter-1.6.0/lib/ci/reporter/rake/cucumber_loader.rb
> -
> -format CI::Reporter::Cucumber test/features/cc_register_complaint.feature
> test/
> features/cc_update_complaint.feature
> test/features/cell_operator_view_complaint.
> feature test/features/citizen_register_complaint.feature
> test/features/citizen_u
> pdate_complaint.feature test/features/citizen_view_complaint.feature
> test/featur
> es/city_official_login.feature
> test/features/city_official_register_complaint.fe
> ature test/features/city_official_update_complaint.feature
> test/features/city_of
> ficial_view_complaints.feature
> test/features/city_official_view_status_reports.f
> eature test/features/GO_update_complaint.feature
> test/features/GO_update_users_c
> omplaint.feature test/features/official_change_password.feature
> undefined method `testcases' for nil:NilClass (NoMethodError)
> c:/ruby/lib/ruby/gems/1.8/gems/ci_reporter-1.6.0/lib/ci/reporter/rake/../../../c
> i/reporter/cucumber.rb:93:in `visit_step'
> c:/ruby/lib/ruby/gems/1.8/gems/cucumber-0.3.91/bin/../lib/cucumber/ast/step_coll
> ection.rb:15:in `accept'
> c:/ruby/lib/ruby/gems/1.8/gems/cucumber-0.3.91/bin/../lib/cucumber/ast/step_coll
> ection.rb:14:in `each'
> c:/ruby/lib/ruby/gems/1.8/gems/cucumber-0.3.91/bin/../lib/cucumber/ast/step_coll
> ection.rb:14:in `accept'
> c:/ruby/lib/ruby/gems/1.8/gems/cucumber-0.3.91/bin/../lib/cucumber/ast/visitor.r
> b:75:in `visit_steps'
> c:/ruby/lib/ruby/gems/1.8/gems/cucumber-0.3.91/bin/../lib/cucumber/ast/backgroun
> d.rb:30:in `accept'
> c:/ruby/lib/ruby/gems/1.8/gems/cucumber-0.3.91/bin/../lib/cucumber/ast/visitor.r
> b:49:in `visit_background'
> c:/ruby/lib/ruby/gems/1.8/gems/cucumber-0.3.91/bin/../lib/cucumber/ast/feature.r
> b:23:in `accept'
> c:/ruby/lib/ruby/gems/1.8/gems/cucumber-0.3.91/bin/../lib/cucumber/ast/visitor.r
> b:23:in `visit_feature'
> c:/ruby/lib/ruby/gems/1.8/gems/cucumber-0.3.91/bin/../lib/cucumber/ast/features.
> rb:25:in `accept'
> c:/ruby/lib/ruby/gems/1.8/gems/cucumber-0.3.91/bin/../lib/cucumber/ast/features.
> rb:13:in `each'
> c:/ruby/lib/ruby/gems/1.8/gems/cucumber-0.3.91/bin/../lib/cucumber/ast/features.
> rb:13:in `each'
> c:/ruby/lib/ruby/gems/1.8/gems/cucumber-0.3.91/bin/../lib/cucumber/ast/features.
> rb:24:in `accept'
> c:/ruby/lib/ruby/gems/1.8/gems/cucumber-0.3.91/bin/../lib/cucumber/ast/visitor.r
> b:19:in `visit_features'
> c:/ruby/lib/ruby/gems/1.8/gems/cucumber-0.3.91/bin/../lib/cucumber/broadcaster.r
> b:9:in `__send__'
> c:/ruby/lib/ruby/gems/1.8/gems/cucumber-0.3.91/bin/../lib/cucumber/broadcaster.r
> b:9:in `method_missing'
> c:/ruby/lib/ruby/gems/1.8/gems/cucumber-0.3.91/bin/../lib/cucumber/broadcaster.r
> b:8:in `map'
> c:/ruby/lib/ruby/gems/1.8/gems/cucumber-0.3.91/bin/../lib/cucumber/broadcaster.r
> b:8:in `method_missing'
> c:/ruby/lib/ruby/gems/1.8/gems/cucumber-0.3.91/bin/../lib/cucumber/cli/main.rb:5
> 8:in `execute!'
> c:/ruby/lib/ruby/gems/1.8/gems/cucumber-0.3.91/bin/../lib/cucumber/cli/main.rb:2
> 6:in `execute'
> c:/ruby/lib/ruby/gems/1.8/gems/cucumber-0.3.91/bin/cucumber:9
> rake aborted!
> Command failed with status (1): [c:/ruby/bin/ruby -I
> "c:/ruby/lib/ruby/gems...]
>
> (See full trace by running task with --trace)
>
> Is the usage for rake features correct?
>
> Regards,
> Pallavi
>
> On Thu, Sep 10, 2009 at 3:14 PM, Graeme Mathieson, Rubaidh Ltd <
>
> mat...@woss.name> wrote:
>
> > Hi,
>
> > Our changes to ci_reporter to support cucumber output have been merged
> > back into Nick's upstream version, and released as 1.6.0. No idea why
> > it's not showing up in the master branch, though!
>
> > We're still using the XML output from ci_reporter for cucumber and
> > rspec features, and it's working well for us. If you have any problems
> > getting it set up, give me a yell and I'll see if I can help.
>
> > Cheers,
>
> > Graeme.
>
> > On Sep 9, 5:43 pm, Charley Baker <charley.ba...@gmail.com> wrote:
> > > It appears there's a forked version of ci_reporter on github that adds
> > > support for cucumber output, find out more here:
> >http://github.com/rubaidh/ci_reporter/tree/master I'm not using
> > > ci_reporter any longer, just straight html output for cuke and rspec, but
> > > the general idea is to set it up in your rake file with the appropriate
> > > requires; there's info in the readme on that github repo.
>
> > > According to the 1.6.0 announcement of ci_reporter on rubyforge this
> > appears
> > > to be the version they've uploaded as the latest gem.
>
> > > hth,
> > > Charley
>
> > > On Tue, Sep 8, 2009 at 11:21 PM, pallavi shashidhar
> > > <pals.sha...@gmail.com>wrote:
>
> > > > Hi there,
> > > > I am looking at using Ci_reporter in watircraft framework. Has anyone
> > tried
> > > > to use it. ?
> > > > We use cucumber on watircraft and has a set of features that needs to
> > be
> > > > run and publish results.
> > > > Basically i have to publish the watircraft results on CI server which
> > > > understands the xml format which is given out by Ci_reporter.
>
> > > > Regards,
> > > > Pallavi
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Watir General" group.
To post to this group, send email to watir-general@googlegroups.com
Before posting, please read the following guidelines: 
http://wiki.openqa.org/display/WTR/Support
To unsubscribe from this group, send email to 
watir-general-unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/watir-general
-~----------~----~----~----~------~----~------~--~---

Reply via email to