Briar

Briar Extends the steps defined in calabash-ios to help you write cucumber Scenarios that interact with complex UI elements like tables, pickers, and sliders.

WARNING: briar is not trying to provide steps that will work for every project

Every project should cultivate its own venacular - a shared language between developers, clients, and users. The steps that briar provides are not meant to be dropped into into your projects (although they can be). Briar provides a library of ruby methods to build application-specific steps from. The steps in the features directory are meant to be examples of what briar can offer.

To see briar in action, take a look at https://github.com/jmoody/briar-ios-example

motivation

DRY: I have several iOS projects that use calabash-cucumber and I found I was rewriting lots of steps and supporting code.

Installation

Requires ruby >= 1.8.7; ruby 2.0 is recommended.

In your Gemfile:

gem 'briar'

In your features/support/env.rb file:

require 'calabash-cucumber/cucumber'
require 'briar/cucumber'

# optional
I18n.enforce_available_locales = false

To integrate briar and your calabash-ios console see: https://github.com/jmoody/briar/wiki/Integrating-Briar-Into-Your-Calabash-Console

briar binary

The briar binary provides useful commands to improve your calabash workflow.

There is detailed help about how to use the .xamarin convention and dotenv to setup your environment.

# help
$ briar help
$ briar help console
$ briar help .xamarin

# open a console against simulators
$ briar console sim6            <== against the current simulator
$ briar console sim7 ipad_r_64  <== changes the default simulator

# open a console against named devices
$ briar console venus
$ briar console neptune

# install the calabash server from a local repo and remove all stale simulator targets in one command
$ briar install calabash-server

# do a clean install of your .ipa on named device
$ briar install pluto
$ briar install earp

# open a cucumber html report in your default browser
$ briar report       <== last run against the simulator
$ briar report venus <== last run against venus

# remove all *-cal targets from the simulator (without resetting the device)
$ briar rm sim-targets

# resolve APP_BUNDLE_PATH auto-detection problems by removing spurious DerivedData directories
$ briar rm dups 
$ briar rm dups briar-ios-example 

# change the simulator version
$ briar sim ipad_r
$ briar sim iphone_4in

Xamarin Test Cloud

There is currently an issue with using briar predefined steps on the XTC:

# fails validation step 
Then I touch the "time" row

version numbers

I will try my best to follow http://semver.org/ when naming the versions.

Why call it briar?

Road Map

I am thinking of dropping all the of predefined steps! Beware! You have been warned!

Contributing

Fork it
Create your feature branch (git checkout -b my-new-feature)
Commit your changes (git commit -am 'Add some feature')
Push to the branch (git push origin my-new-feature)
Create new Pull Request