0.0
No commit activity in last 3 years
No release in over 3 years
Library to maintain a forking queue of Cucumber processes, with optional VNC displays. Designed for JRuby and Windows.
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
 Dependencies

Development

>= 0
~> 10
>= 0

Runtime

>= 0.5.3
>= 2.3.2
>= 0.1.1
 Project Readme

jcukeforker

Forking cukes and VNC displays.

Jcukeforker is a fork of cukeforker desgined for jruby and windows. Jcukeforker > 0.3 should work on windows.

Gem Version Build Status

NB!

If you're using cukeforker with selenium-webdriver and Firefox, all versions prior to 2.40 has a bug where custom Firefox profiles created in a forked process would not get cleaned up. Please make sure you're using selenium-webdriver >= 2.40 to avoid this.

Usage

    # parallelize per feature
    JCukeForker::Runner.run Dir['features/**/*.feature'],
                           :max        => 4,                    # number of workers
                           :out        => "/path/to/reports",   # output path
                           :format     => :html,                # passed to `cucumber --format`,
                           :extra_args => %w[--extra arguments],# passed to cucumber,
                           :vnc        => true                  # manage a pool of VNC displays, assign one per worker.

    # parallelize per scenario, with one JUnit XML file per scenario.
    JCukeForker::Runner.run JCukeForker::Scenarios.tagged(%W[@edition ~@wip])
                           :extra_args => %W[-f JCukeForker::Formatters::JunitScenarioFormatter --out results/junit]

    # setup with vncserver and screen recording
    JCukeForker::Runner.run Dir['features/**/*.feature'],
                            :vnc       => %W[-geometry 1280x1024 -depth 24 -dpi 96],
                            :record    => {:ext => 'mp4', :codec => 'mpeg4', :frame_size => '1280x1024', :frame_rate => '5'}

Note on Patches/Pull Requests

  • Fork the project.
  • Make your feature addition or bug fix.
  • Add tests for it. This is important so I don't break it in a future version unintentionally.
  • Commit, do not mess with rakefile, version, or history. (if you want to have your own version, that is fine but bump version in a commit by itself I can ignore when I pull)
  • Send me a pull request. Bonus points for topic branches.

Copyright

Copyright (c) 2011-2014 Jari Bakken. See LICENSE for details.