aurelien-reeves on main
Remove custom issue templates (… (compare)
mattwynne on use-shared-issue-templates
Remove custom issue templates … (compare)
github-actions[bot] on v11.0.0
aurelien-reeves on v11.0.0
Update release workflow accordi… (compare)
aurelien-reeves on main
Update release workflow accordi… (compare)
aurelien-reeves on v11.0.0
Update test workflow to not fai… Fix workflow Update ruby versions executed o… (compare)
aurelien-reeves on main
Update ruby versions executed o… (compare)
aurelien-reeves on main
Fix workflow (compare)
aurelien-reeves on main
Update test workflow to not fai… (compare)
aurelien-reeves on v11.0.0
aurelien-reeves on main
Prepare release 11.0.0 (#228) … (compare)
maxInstances
property
capabilities.browserName
, it'll launch 3 firefox sessions and 3 chrome sessions
Longtime Cucumber user and Ruby enthusiast.
On a serious note, I'm struggling with when I should delete data and where I can (e.g. After
hook)?
Scenario: As John I verify I feel good once I put on shoes
Given: I create a person named John
When: I put my shoes on
Then: I feel refreshed
And: I delete person named John using an API call
In this scenario I am setting up my person named John from the UI, however, I don't want this person hanging around in my DB, so I'm adding a step to delete this individual. The scenario is not about deleting John, but feeling good about putting on shoes. So, if for some reason my deletion fails, then the test fails which is incorrect. So, can I abstract this step and place it into an After
hook using a variable that I store John in? What if I have multiple scenarios creating multiple Johns, can I still abstract this step?
I know this might sound jumbled, so please tell me to provide further or clearer details.
Thanks.
After
hook works well enough for this kind of thing.Given(/^I create a person named John$/) do
# Instance variable so that future steps can use this person
@person_for_test = create_new_person('John')
# Other steps may have already created people
@people_created ||= []
@people_created << @person_for_test
end
After do
# Possible that no person creating steps were called/reached
if @people_created
@people_created.each do |person|
delete_person(person)
end
end
end
Given "I am {string}" do |name|
cucumber.yml was found, but could not be parsed with ERB. Please refer to cucumber's documentation on correct profile usage.
#<Errno::EEXIST: File exists @ dir_s_mkdir - ./features/reports/2017-10-26__0925_32s>cucumber.yml was found, but could not be parsed with ERB. Please refer to cucumber's documentation on correct profile usage.
#<Errno::EEXIST: File exists @ dir_s_mkdir - ./features/reports/2017-10-26__0925_32s>
<%
@time = Time.now.strftime("%Y-%m-%d__%H%M_%Ss")
Dir.mkdir('./features/reports/') unless File.exists?('./features/reports/')
@report_path = "./features/reports/#{@time}/"
@screenshot_path = "./features/reports/#{@time}/"
@new_dir_setup = -> { Dir.mkdir(@report_path) unless File.exists?(@report_path) }
ENV['SERVER_URL'] = ENV['SERVER_URL']
%>
# Cucumber Base Profile components:
common: RESET_BETWEEN_SCENARIOS=1 SERVER_URL=<%= ENV['SERVER_URL']%> -f progress -r features
html_report: <%@new_dir_setup.call%> -f html --out=<%= @report_path%>web_test_report<%= ENV['TEST_ENV_NUMBER']%>.html SCREENSHOT_PATH=<%= @screenshot_path%>
ENV['SERVER_URL'] = ENV['SERVER_URL']
isn't going to do much for you.
html_report
profile is used.
@TesterAB_twitter Because Cucumber is Semantically Versioned, there should not be any changes from 2.4 to 2.99 that would be a problem for you (i.e. breaking changes). You will quite possibly encounter them at 3.0 but if you plan on upgrading to that point anyway, then you might as well go straight there and deal with whatever comes up.
Here is a handy blog post about upgrading to Cucumber 3.0 https://cucumber.io/blog/2017/09/21/upgrading-to-cucumber-3
Transform
s, which are removed in v3.0.0, see cucumber/cucumber-ruby#1190
cucumber --tags @allfeatures -f json -o reports/results.json
Scenario:
Given we are working with the number "7"
Then we can do stuff with it
And even more stuff
Given /^we are working with the number "(\d+)"$/ do |number|
@current_number = number
end
Then /^we can do stuff with it$/ do
puts "Doing stuff with #{@current_number}"
end
Then /^even more stuff$/ do
puts "Doing more stuff with #{@current_number}"
end