similar to: spec_ui problems

I am having inconsistent output with multiple options in the spec.opts file. I can, for instance, pass --color or --colour, or, separately, use --drb. But when combining them I get: /opt/local/lib/ruby/1.8/optparse.rb:1381:in `complete'': invalid option: --options --color --drb (OptionParser::InvalidOption) from /opt/local/lib/ruby/1.8/optparse.rb:1379:in `catch''

I am using Cucumber 0.2.3 and am having problems running a single feature. In particular, the cucumber Textmate bundle was not working so I traced it back and discovered that I could not run single files or features from the command line either. My setup has the following line in cucumber.yml default: -r features/support/env.rb -r features/support/plain.rb -r features/steps

Hi, Hi I am trying to use RSPEC on windows and i keep getting the following error "You must gem install win32console to use colour on Windows" I have installed this Gem but i am still getting the same error. The file that error is coming from is: C:\ruby\lib\ruby\gems\1.8\gems\rspec-0.8.2\lib\spec\runner\formatter\base_text_formatter.rb Do i need to put this line of code in? Where

Does anyone else have issues running rspec textmate bundle? I''ve got revision 2997, but the blasted thing just won''t run. It is checked out to my /Users/zdennis/Library/Application Support/TextMate/Bundles/RSpec.tmbundle When it runs I get the below error... "textmate" is not a valid class name

In case anyone else is trying to make this work, here is what I did (Before 0.7.4 I had patched the regex in zentest redgreen, but that is not used any more) To use directly, it is very simple. In rspec_autotest/lib/ rspec_autotest.rb, add a -c to the spec_command in the initializer function: @spec_command = "spec -c --diff unified" This won''t help however if you want

I''m evaluating what to use for integration testing: SafariWatir - integrates nicely with RSpec - doesn''t work with Ajax because of Safari event firing issues Selenium - Works with Ajax - doesn''t integrate with RSpec What is the best guess timeframe for RSpec integration testing? Will it be able to test Ajax application in the early iterations? Thanks, Brian Yamabe

I tried running a spec with command-r in TextMate and got: /Library/Application Support/TextMate/Bundles/RSpec.tmbundle/Support/ lib/spec_mate.rb:1:in `require'': No such file to load -- rubygems (LoadError) from /Library/Application Support/TextMate/Bundles/ RSpec.tmbundle/Support/lib/spec_mate.rb:1 from /tmp/ temp_textmate.GplhPr:3:in `require'' from

rake spec:views does not run the specs in my views folder. I can run them with spec <path>. Is there something I missed? ---Brian Yamabe

The "rspec" rake task collects all _spec files in the spec directory, and excludes the "watir" directory. Is this indicating a preference for using Watir over Selenium? I would like it better to standardize on something more neutral, ''ui'' perhaps? /Marcus -- Marcus Ahnve http://marcus.ahnve.net

Hi I just did an update to lates trunk ================= context "Given a generated venue_spec.rb with fixtures loaded" do fixtures :venues specify "fixtures should load two Venues" do Venue.should have(2).records end end ================== gives me ========== 1) TypeError in ''Given a generated venue_spec.rb with fixtures loaded fixtures should load two

Hi, I was trying to use the autorun feature of rspec but noticed that when I run the command to kick off the ruby scripts it picks up the options that I give to the command. ''myRubyBin -j optionValue'' This then fails with this error, /usr/lib/ruby/1.8/optparse.rb:1448:in `complete'' : invalid option: -j ( OptionParser::InvalidOption ) from

I''ve got rspec and zentest installed as well as the rspec rails plugin, and my model/controller specs all pass and work well. I can''t seem to get views to work though - 100% of the specs fail with: NoMethodError in ''/users/show.rhtml should render attributes in <p>'' protected method `render'' called for

For some reason rake spec is totally crapping out on me. I don''t know what I did to make it break, the only thing I tried new was install haml, but even after removing it there is still a stack trace. Here is what I am getting- sparta at phalanx ff $ rake spec (in /Users/sparta/Projects/work/idastudios/ff)

I have the latest version of rspec and rails-rspec installed. I''m using the debian versions of ruby and rails. On a new project after a generate an "rspec_model" and then try to run "rake spec", I get the following error: dan at dan-server:~/projects/cw/registration$ rake spec (in /home/dan/projects/cw/registration)

I''m trying to get Rspec working. Using the installing 1.0.7 & the Rails plugin, I tried one of the examples on Rspec''s website and produced the following error: ############################################################################ Your RSpec on Rails plugin is incompatible with your installed RSpec. RSpec : 1.0.7 (r2332) RSpec on Rails : r2331 Make sure

Hi We've found that when using parse_args(..., positional_arguments=FALSE), it is permissible to invoke our script with either "--myfoo=bar" or "--myfoo bar"; that is, whether or not the equals sign is present makes no difference, and in fact both usage forms are demonstrated in the optparse vignette. However, we've found that when using parse_args(...,

Hi, For example, I have several variables in php, like var1 = 1, 2, 3, 5, 6 var2 = 3, 1, 8 var3 = 8, 10, 4, 0, 9, 1 I sent the arguments to R, with this line: '/usr/bin/R --vanilla --slave --args '.$var1.' '.$var2.' '.$var3.' < script.r' In my "script.r" I can read the arguments whit this line: args=(commandArgs(TRUE)) args=as.numeric(args) args

I''m going through Peepcode''s Rspec Basics for an overview. He''s just doing a simple spec: class PeepCode end describe PeepCode do it "should be awsome" do end end So running spec spec/simple_spec.rb should produce according to his screen cast: 1 example, 0 failures, 1 not implemented but I only recieve: 1 example, 0 failures Also spec

Hi, A user of my `optparse` package discovered a bug in Rscript's parsing of [args]. (https://github.com/trevorld/optparse/issues/24) I've reproduced the bug on my machine including compiling and checking the development version of R. I couldn't find a mention of it in the Bug Tracker or New Features. Can be minimally reproduced on the UNIX command line with following commands:

Hey guys, Does anyone have an example of a REALLY simple shell script in R. Basically i want to run this command: library(MASS) wilcox.test(list1,list2,paired=TRUE,alternative=c("greater"),correct=TRUE,exact=FALSE) in a shell script something like this: #!/bin/bash R library(MASS) for i in *.out do wilcox.test($i,${i/out}.out2,paired=TRUE) >> $i.out done that i can run on a