This document discusses BDDfire, a Behavior-Driven Development framework for Ruby. BDDfire includes Capybara for writing acceptance tests, Poltergeist for headless browser testing, parallel_tests for parallel test execution, and tools like Rubocop, CukeSniffer, Yard, RestClient, Axe, Gatling, and Docker to integrate with other development and testing processes. The workshop demonstrated how to set up a BDD project with BDDfire, write tests using Gherkin syntax and predefined steps, and run tests on different browsers and servers.

1. Software quality assurance days
19 Международная конференция
по вопросам качества ПО
sqadays.com
Санкт-Петербург. 20–21 мая 2016
Владислав Романенко
Intellectsoft. Минск, Беларусь
Игры с огнём: знакомимся с BDD
и Cucumber фреймворком BDDfire

2. QA-инженер в Intellectsoft
В тестировании >2 лет,
до этого работал инженером
географических информационных
систем (ГИС)
Тестирую мобильные и веб
приложения
Сертификат ISTQB Foundation level
v.romanenko_
laechoppe@gmail.com

3. BDD is like Jazz.
There is no
authoritative
definition of what it is

4. BDD
is a process designed to aid
the management and the delivery
of software development projects
by improving communication
between engineers and business
professionals

6. w o r k s h o p
1.

7. 1.
BA
QA
dev

8. 2.=> Cucumber format
Given…
When…
Then…
Gherkin:

9. 3.
ruby
=> step definitions

10. 3. => tests execution

12. - prevent the bug
To do list:

13. - exhaustive list
of scenarios
To do list:

14. What’s to avoid?

15. What’s to avoid?
- Leaking scenarios
Given When Then
A BX

16. What’s to avoid?
- All is end-to-end

17. What’s to avoid?
- Fixtures

18. BDD is not:
Equal to
Functional testing

19. BDD is not:
Only about
testing

20. a quick fix,...
BDD is not:

21. ...an investment
BDD is:

22. SQA DAys-18 talk:
“Behat-trick:...”

23. w e b d r i v e r

24. bddfire:
Write your tests,
not framework

26. Why “Cucumber”?

27. bddfire:
Capybara
Selenium Webdriver
Docker
RestClient
Poltergeist
Gatling
Appium
Saucelabs
Relish, Yard
Axe accessibility engine
Rubocop

28. Installation:
$ gem install bddfire
$ bddfire fire_cucumber
$ cd cucumber & bundle install

29. Predefined steps:
Given I am on “url”
When I click on element having text “foo"
Then The page title is “bar"

30. Predefined steps definitions:
Then(/^page contains "(.*?)"$/) do |element|
page.should have_css(element)
end
Then(/^I should see "(.*?)"$/) do |text|
page.should have_content text
end

31. Scenario: Signing in as an existing user
Given I am on "http://test.org/auth"
When I fill in "email" with the text "vlad@r.by"
And I fill in "password" with the text "qwerty"
And I click on element having text "Sign In"
Then The page title is "Homepage"
Hello world scenario:

32. Natural risks
forest fire
avalanche
Project overview:
Actions
Rescue people
Put out the fire
Warn alpinists

33. 1. Features
Project structure:
Scenario: I can see the quantity of risks in each state
Given I'm a rescue team member
When I observe the table of risks
Then I see the correct quantity of risks by state

34. Project structure:
When (/^I want to view the details of a Risk/) do
risk_num = rand(1...10).to_s
link = '#/steps/' + risk_num + '/details'
find(:xpath,"(//*[@href='#{link}'])[1]").click
end
2. Step definitions

35. Project structure:
Capybara.configure do |config|
config.run_server = false
...
config.default_selector = :xpath
config.default_wait_time = 60
end
3. Support code

36. Project structure:
After do
page.evaluate_script('window.confirm = function()
{ return true; }')
find(:xpath, '//*[@ng-click="vm.logOut()"]').click
end
4. Hooks

37. Project structure:
default: -p selenium
html: --format --out reports/test.html
api : DRIVER=poltergeist --tags @api
chrome: DRIVER=chrome
pretty: -f pretty
5. Configuration file

38. Project structure:
source 'http://rubygems.org'
gem 'cucumber'
gem 'capybara'
gem 'bddfire'
gem 'selenium-webdriver'
6. Dependencies

39. Project structure:
6. Reports / Docs folders

40. What’s included?
1. Capybara
Acceptance test framework for web
applications.
It simulates how a real user would
interact with the app

41. Why “Capybara”?

42. Why “Capybara”?
Webrat => Capybara

43. What’s included?
1. Capybara
Given(/^I am on homepage$/) do
visit('http://risk.piemont.org/#/login')
end
Given(/^I want to see Risk timeline/) do
find(:xpath,'//*[@ui-sref="risk.timeline"]').click
end

44. What’s included?
2. Poltergeist
allows runNing Capybara tests on a headless browser

45. What’s included?
2. Poltergeist
@poltergeist
Scenario: Signing in as an existing user
Given I am on "http://test.org/auth"
When I fill in "email" with the text "vlad@r.by"
And I fill in "password" with the text "qwerty"
And I click on element having text "Sign In"
Then The page title is "Homepage"

46. What’s included?
3. parallel_tests

47. What’s included?
4. BrowserStack
Cloud-based cross-browser testing tool

48. What’s included?
4. BrowserStack

49. What’s included?
5. Rubocop
Code style checker
based on the community-driven Style Guide

50. What’s included?
5. Rubocop

51. What’s included?
6. CukeSniffer
Static analysis tool for the Cucumber.

52. What’s included?
6. CukeSniffer

53. What’s included?
7. Yard
A Requirements Documentation Tool

54. What’s included?
7. Yard

55. What’s included?
8. RestClient
Simple HTTP and REST client for Ruby

56. What’s included?
8. RestClient
Given I send a GET request for "<your_uri>"
Given I send a GET/PUT/POST/DELETE request
for "<your_uri>" with the following:
"""
<your_payload>
"""
Then the response should be JSON

57. What’s included?
9. Axe

58. What’s included?
9. Axe

59. What’s included?
10. Gatling
load testing framework

60. What’s included?
10. Gatling

61. What’s included?
11. Docker
platform for distributed applications

62. Summary:
$ gem install bddfire
$ bddfire fire_cucumber
$ cd cucumber & bundle install

63. Thanks!
Questions?
v.romanenko_
laechoppe@gmail.com