The following should get you started on setting up your development environment. As a prerequisite you will need a Ruby environment (Ruby version >= 2.2, 2.5 recommended). We recommend to use RVM to create an isolated development environment. On Windows the RubyInstaller for Windows is probably the easiest way to get started. In this case you will need the DevKit as well.
The following sections list the most important commands you will need for development.
$ gem install bundler
$ bundle install
Get a list of all available build tasks:
$ bundle exec rake -T
Build the Landrush gem:
$ bundle exec rake build
Clean all generated files:
$ bundle exec rake clean clobber
Run the test suite:
$ bundle exec rake test
|The unit tests utilize minitest as test harness. Tests are mainly written in Spec style. To make testing simpler, each test will be configured against a newly created temporary working directly which will be deleted on teardown. Refer to test_helper.rb to see how this setup and teardown works.|
Run a single test file:
$ bundle exec rake test TEST=<path to test file>
Run cucumber/aruba acceptance tests:
$ bundle exec rake features
|The acceptance tests currently work only for OS X, out of the box. On Linux, one has to manually configure the host visibility for the TLD landrush-acceptance-test. See Linux in the Visibility on the Host section of the Usage guide. On Windows, the acceptance tests won’t work due to a bug in Aruba.|
Run a single cucumber/aruba acceptance tests:
$ bundle exec rake features FEATURE=features/<feature-filename>.feature
To build the documentation you can execute:
$ bundle exec rake html
which will build the HTML documentation into the folder build/html.
$ bundle exec guard
and your HTML documentation will be automatically updated on each change to an Asciidoc source file.
Run the vagrant binary with the Landrush plugin loaded from your local source code:
bundle exec vagrant landrush <command>