BDDfire: Automate Mobile & Web apps with less code. An instant Ruby-Cucumber BDD framework which supports various popular open-source libraries like Capybara, Selenium-WebDriver, Poltergeist, Relish, Cuke_sniffer, Rubocop, Appium, Saucelabs, Browserstack. Generate default toolkit around BDD with cucumber and friends. BDDfire can do API testing with RestClient. It also added support for Docker, Gatling, Axe Accessibility Engine
BDDfire: Instant Ruby-Cucumber Framework with Docker, Gatling, Accessibility, REST API Testing Support
Assuming you got Ruby installed. You can run
$ gem install bddfire
or include it into the Gemfile
Instant Ruby Cucumber Framework
$ bddfire fire_cucumber
This will create 'cucumber' directory and one command will install Ruby Cucumber framework with all possibly supported tools in the 'cucumber' directory.
This will create all the directories and files to support following tools
- Poltergeist: PhantomJS based headless driver for capybara
- Docker support to execute scenarios inside docker containers
- Run scenarios in parallel 10 processes and rerun failed scenarios.
- Appium : Mobile test automation Framework
- API Testing : BDDfire uses RestClient to perform API testing
- Saucelabs : Cloud testing framework
- Browserstack : Cloud testing framework
- TestingBot : Cloud testing framework
- Relish : Living Documentation
- Yard : Cucumber documentation
- Rubocop : Ruby code review tool
- CI Support Script
Install & Run BDDfire framework
Install your skeleton framework with BDDfire
$ bddfire fire_cucumber $ bddfire fire_load $ bddfire fire_accessibility
Now you should have your framework ready inside 'cucumber' directory. Just install predefine Gems or you can add your own Gems. You can see animated GIF above how it works.
$ cd cucumber $ bundle install
Once installed, you can run cucumber with multiple capybara driver. Here is demo of running test with Poltergeist and FireFox Driver
BDDfire allow us to use predefined steps so that we don't have to write more code while writing cucumber steps. BDDfire has following predefined steps which can be used anytime during your project.
Browser Based Pre-defined-steps
You can useBrowser based steps
Poltergeist Based Pre-defined-steps
You can use headless Poltergeist based headless Poltergeist based steps
Parallel Cucumber & Re-run Failed
You can run entire test suite in 10 different processes but you can increase number of processes. The reports are generated for each process. If any scenario failed it will re-run. It will use poltergeist by default but you can change in Rakefile
$ bundle exec rake parallel_cucumber
You can use selenium driver to run scenario in browser [firefox].
$ bundle exec rake selenium
You can use PhantomJS based Capybara driver Poltergeist driver.
$ bundle exec rake poltergeist
You can run your scenarios in Google Chrome
$ bundle exec rake chrome
REST API Testing
You can run your scenarios in Google Chrome. Just tag your scenario/feature with @api and You can use inbuilt predefined API Steps API based
$ bundle exec rake api
Cloud Testing Frameworks
Please enter your USERNAME and KEY in the env.rb file
$ bundle exec rake sauce/browserstack/testingbot
Run Appium server in the background.
$ npm install $ ./node_modules/.bin/appium
Now run cucumber with appium. Make sure you updated env.rb file with capabilities you want to use for Android.
$ bundle exec cucumber -p appium ADB_SERIAL=serial_number
Now run cucumber with appium iOS. Make sure you updated env.rb file with capabilities you want to use for iOS
$ bundle exec cucumber -p appium
You can use cuke_sniffer to detect smells in your Cucumber. It will generate reports in the cuke_sniffer.html in the 'reports' directory.
$ rake cuke_sniffer
You can use rubocop to detect ruby errors in your Ruby file
$ rake rubocop
This will report all the offence in rubocop.
We can run our cucumber scenario inside Docker containers. Assuming you have Docker installed. Check your Docker installation before using.
$ bundle exec rake docker
This will build Docker image 'bddfire-ci' and run cucumber scenarios inside container 'bddfire-ci'.
You can use Gatling setup to execute load tests against your endpoints. Simply change 'load/user-files/simulation/SampleLoadTEST.scala' file and puts your URL to Test as base URL.
$ cd load $ sh gatling_local.sh
This will run load tests against your url. You are free to record new simulations. Once finished there will be link to HTML report at the end.
There is CI integration to plug it with Jenkins.
Accessibility Testing : Axe
We can run accessibility checks on our web page using BDDfire. You have to pass URL as environment variable e.g
$ cd accessibility $ bundle exec cucumber -r features URL="http://www.google.co.uk"
Accessibility related Pre-defined-steps
You can also use Accessibility steps
Watch Entire Demo
- Add more and more steps so that user won't need to write more code
- Add examples to show use of native app automation
- Integration with AWS Device Farm or BBC HiveCI
Copyright © 2016 Shashikant Jagtap, http://shashikantjagtap.net
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
- Fork it ( https://github.com/Shashikant86/bddfire/fork )
- 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 a new Pull Request