Writing code for your test cases
This page will describe how you can start putting actions behind the steps you have written in `Writing_gherkin_test_cases_in_cucumber`.
Contents
Making a custom step
Let's start by creating a new scenario in example.feature
:
@example1337 Scenario: example1337 - Going to the Execute scenarios page on TA.info Given I am on the website testautomation.info When I click on Execute scenarios Then I should see text "Writing code for your test cases"
And run the scenario in the console: bundle exec cucumber -t @example1337
. This will result saying that there are 3 undefined steps, with the code to use to define the steps. Copy this code into the interaction_steps.rb
file.
To copy text from console in windows, right click in console and select Mark. Then select the area you want to copy and press Enter. The selected text is now on the clipboard and can be pasted using Ctrl+V.
Now we have the step definitions written down, we can start adding code to the steps. First create a new file ./features/step_definitions/tutorial_steps.rb
and add the following:
Given(/^I am on the website testautomation\.info$/) do browser.goto 'http://www.testautomation.info/' end When(/^I click on Execute scenarios$/) do browser.find('n-5.-Execute-scenario.27s').click end Then(/^I should see text "([^"]*)"$/) do |arg1| browser.wait(:text => /#{arg1}/) end
Now run the scenario again: bundle exec cucumber -t @example1337
Advanced steps & code
Regular expressions in Step definitions
Step definitions are made using regular expressions, meaning, you can put in code to catch multiple cases. For example, when you write (.*)
it mean any character of any length can be here.
To learn more about regular expressions, go to http://rubular.com/
Lapis Lazuli
In the example above some simple code is used to change page and to click on an element. The are many many more options to use Lapis Lazuli. Besides finding an element or waiting for an element to become present. You can also select multiple elements and then interact with a random element.
During your time working with test automation you will start using all these different options. You can find the documentation on this same Wiki. See: Lapis_Lazuli:Usage
Debugging
Some scenario's take a long time to execute and something is going wrong at the end of that scenario. Instead of running that scenario over and over again, it is easier to debug the code from the step that is going wrong.
More info: debugging_code_in_test_automation