Upgrade to RSpec3.0 complete, all specs green
Merge pull request #14 from NikitaAvvakumov/upgrade_to_rspec_3.0

Upgrade to RSpec3.0 complete, all specs green
initial commit of cucumber chore

based on user story https://www.pivotaltracker.com/story/show/76232594
initial setup of admin_partners features
changes to active admin model to comply with feature requests
Fix incorrect description of admin_partner feature

based on user story https://www.pivotaltracker.com/story/show/76232594
fixed description of admin_partner feature incorrectly discussing
a WebSiteOne feature as noticed by NikitaAvvakumov
further refine admin_partners feature description

based on user story https://www.pivotaltracker.com/story/show/76232594
renamed Province code and names created to match db seed in production

based on user story https://www.pivotaltracker.com/story/show/76232594
renamed the Province codes and names to what is required to be used in
production in order to avoid refactoring in the future if stronger
validations are introduced for the Province model.
removed commenting on Partner model that detracts from the tests

based on pivotal story https://www.pivotaltracker.com/story/show/76232594
fix typo and use newer rspec syntax refactor

https://www.pivotaltracker.com/story/show/76232594
fix problems with the code identified by NikitaAvvakumov
during PR code review
upgrade capybara and refactor step definition to comply with rspec3

based on user story https://www.pivotaltracker.com/story/show/76232594
1. Upgrade Capybara from 2.2.1 to 2.4.1 including associated
   dependencies nokogiri and miniportile to complly with rspec3
2. Change syntax of step definition to compy with rspec3