similar to: Passing variables to custom formatters

Hi, I''m working on update my local Cucumber to the latest version. But it seems the old formatter APIs(step_failed, scenario_executed, etc.) don''t work any more. Are there some documents or even Cucumber source code I can refer to? Thanks in advance, Liu -------------- next part -------------- An HTML attachment was scrubbed... URL:

I am trying to write a custom formatter to update a database record based on example results. Having a lot of trouble, so I thought to ask if anyone has a custom formatter that writes results to a database or outputs results in JSON or some other programmatic format. A working example will go a long way in helping me work thru my own use case. Thanks -------------- next part -------------- An

I''ve always been a little bit bemused by the default ruby test/unit and rspec output. Basically, what I want is a progress bar and that any errors and warnings be displayed immediately. I also want warnings to be printed for slow specs. When using color, I want the entire progress bar printed in green if everything is good, yellow if there has been a warning, and red if there has been an

Questions concerning spec.opts: 1. Am I correct in believing that each option should go on a separate line of spec.opts in the rails spec directory? If this is so, why is it so? 2. Using a formatter in spec.opts doesn''t seem to work. Here is my spec.opts file: --colour -f s and this is what happens when I run the rake task: Couldn''t find formatter class s Make

Is there a proper naming scheme for custom formatters? Thanks -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://rubyforge.org/pipermail/rspec-users/attachments/20111213/59572c22/attachment-0001.html>

Hello. I''m using RSpec with Watir to do some automated tests on IE. I''ve ran into problem, where I want to make a screenshot of a browser window when example fails. For that I made custom formatter where in extra_failure_content i''m invoking screenshot taking methods. Now, everything works like a charm, as long as I''m not using after :each. I remember that I

Hi I use the ci_reporter gem for builds on my CI machine (hudson). Prior to rspec 2.4, environment options would override commandline options. So the gem used this to change the formatter and require its files. In 2.4, that order has been reversed. the thing is 2.4 supports multiple formatters, so there is another suggestion. RSpec::Core::ConfigurationOptions def parse_options

All, I''ve found that the html view for the rspec formatter falls to pieces with Rails 2.02 and rspec 1.10. Has anyone else run into this trouble? Here''s a monkey patch that fixes the problem. A more elegant fix would be in order, but this gets the job done: Index: /Users/timcharper/www/exchange/vendor/plugins/rspec/lib/spec/runner/formatter/text_mate_formatter.rb

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

rake spec seems to work fine, but I keep getting a usage error at the end of the spec run: /usr/local/bin/ruby -I"/usr/local/lib/ruby/gems/1.8/gems/rspec-0.6.4/ lib" "/usr/local/lib/ruby/gems/1.8/gems/rspec-0.6.4/bin/spec" Usage: spec [options] (FILE|DIRECTORY|GLOB)+ --diff Show unified diff of Strings that are expected to be equal when

I figured most of it out. The Spec::Rails stuff was something in the code which has been fixed by revision 3099. The test methods partially make sense. Since the test/unit code has been integrated, methods with test in them are automatically turned into specs. However, the test? method is in a lib file that isn''t directly loaded into the specs. It is a convenience method: def

Recently as a result of using Git I''ve noticed a number of inconsistencies in the RSpec codebase with respect to whitespace (mixed line endings, mixed use of spaces and tabs for indentation, and trailing whitespace at the end of lines). I never would have noticed, but Git produces nice colorized diff output which highlights these kinds of inconsistencies. I wanted to ask if the

Is it possible to read which formatter is being used? For instance if - f d is used to output additional information or is there a better way to do that?

Hello guys, I''m getting this weird error when trying to run the specs using "rake spec": /home/mauricio/NetBeansProjects/talkies/vendor/rails/actionpack/lib/action_controller/test_process.rb:471:in `method_missing'': undefined method `full_description'' for #<Spec::Rails::Example::ControllerExampleGroup::Subclass_73::Subclass_9:0x7f5fdca4a810>

While looking into spec_ui, I decided to run the examples. The watir example works a little, but always chokes on the ''better than fudge'' spec (failure output below). Also, is there any command to pause the "browser"? If my connection slows, the test gets out of whack. The selenium example fails right away (output below). I do have the 0.9.0 selenium-rc

I''m doing some housekeeping and just realised that the rdoc formatter produces gibberish: http://rspec.rubyforge.org/rdoc/files/EXAMPLES_rd.html Will anyone protest if I just go ahead and remove it? (I can''t imagine anyone using it, especially with the much better HTML formatter) Aslak

Where and how do you put custom logger statements in cucumber? I understood (more or less) how to do this in rspec in the spec_helper file but I do not know where to start with cucumber. I want to add a simple identifying text line in the log file to assist in picking through the output. Something akin to: Running Scenario: X Feature I should have this logged .... Feature This should

I recently noticed the HTML formatter for the story runner, but I''m unable to figure out how to make it function. ''ruby stories/all.rb --format html'' seems like it should work, in that --help works as expected, but I still get only plain text output. Maybe it''s not been wired up yet and/or this is a bug. Maybe I''m just being dumb. I have no clue at

Hi! I wonder does anybody planning to go beyond the default html formatter/report? The current html report is nice and green but what about to go a little silly and enable also user input. For example to let customer to add a new pending spec, comments etc. I feel it might be mentally easier for some customers to jump into spec world when it is possible to give input at "the same

Hi all I''d like to keep the 10 slowest results shown when using --profile as an artifact of my ci builds. Is there some way to direct this particular output to a file/folder? Is there anything that produces an html version of this output e.g. a formatter? I''d be interested to know why --profile is not a formatter (its not a formatter in I''m using Jenkins for Ci and