Thanks for installing your Ruby-Cucumber framework with BDDfire.
This will create all the directories and files to support following tools
- Capybara
- Selenium-Webdriver
- 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
Now you should have your framework ready inside 'cucumber' directory. Just install predefine Gems or you can add your own Gems.
$ cd cucumber
$ bundle install
Once installed, you can run cucumber with multiple cabybara driver
#Usage
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.
You can useBrowser based steps
You can use headless Poltergeist based headless Poltergeist based steps
Just tag your scenario/feature with @api and You can use inbuilt predefined API Steps API based
You can also use Accessibility steps
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
###Headless Poletergeist You can use PhantomJS based Capybara driver Poltergeist driver.
$ bundle exec rake poltergeist
###Chrome Driver You can run your scenarios in Google Chrome
$ bundle exec rake chrome
You can run your scenarios in Google Chrome
$ bundle exec rake api
![image](https://github.com/Shashikant86/bddfire-gifs/blob/master/bddfire_rest_api.gif
###Cloud Testing Frameworks Please enter your USERNAME and KEY in the env.rb file
$ bundle exec rake sauce/browserstack/testingbot
###Appium:
Run Appium server in the background.
$ npm install
$ ./node_modules/.bin/appium
OR
$rake start_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
###Cuke_sniffer
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
###Rubocop
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.
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"
"# bddfire-automation-fun"