selenium-cucumber 0.0.9 → 0.1.0

data/Example/features/assertion_steps_Ex.feature

@@ -0,0 +1,121 @@
+
+Feature: Assertion Steps
+        As a user I should able to verify using assert steps
+ 
+ 	Scenario: Open test page
+ 		Given I open test page
+ 		
+ 	Scenario: verify page title
+		Then I should see page title as "Test Page for selenium-cucumber"
+ 		
+
+	Scenario: verify element text
+
+		Then element having id "dbClick" should have text as "Double-click this paragraph to trigger a function."
+ 		Then element having name "javascript_alert_msg" should have text as "Click the button to display a confirm box."
+ 		Then element having class "form_name" should have text as "Simple sample form with input elements"
+ 		Then element having xpath ".//*[@id='frm']/fieldset/p[1]/label" should have text as "Text input (first name)"
+ 		
+ 		Then element having id "dbClick" should not have text as "Double-click this"
+		Then element having name "javascript_alert_msg" should not have text as "Click the button"
+		Then element having class "form_name" should not have text as "Simple sample"
+ 		Then element having xpath ".//*[@id='frm']/fieldset/p[3]/label" should not have text as "xyz"
+
+	Scenario: verify element text - negative test 1
+
+		Then element having id "dbClick" should have text as "Double-click this"
+
+	Scenario: verify element text - negative test 2
+
+		Then element having name "javascript_alert_msg" should not have text as "Click the button to display a confirm box."
+
+ 	Scenario: verify element accesibility
+
+ 		Then element having id "submit" should be enabled
+ 		Then element having name "btn_reset" should be enabled
+ 		Then element having class "cls_pwd" should be enabled
+ 		Then element having xpath ".//*[@id='try_it']" should be enabled
+
+ 		Then element having id "disabledBt_id" should be disabled
+ 		Then element having name "disabledBt_name" should be disabled
+ 		Then element having class "df_class" should be disabled
+ 		Then element having xpath ".//*[@id='df_id']" should be disabled
+
+	Scenario: verify element accesibility - negative test 1
+
+		Then element having id "submit" should be disabled
+
+	Scenario: verify element accesibility - negative test 2
+
+		Then element having id "disabledBt_id" should be enabled
+
+ 	Scenario: verify element visibility
+
+ 		Then element having id "hiddenElement" should not be present
+ 		Then element having name "he_name" should not be present
+ 		Then element having class "he_class" should not be present
+ 		Then element having xpath ".//*[@id='hiddenElement']" should not be present
+ 		
+		And I wait for 10 sec
+
+ 		Then element having id "hiddenElement" should be present
+ 		Then element having name "he_name" should be present
+ 		Then element having class "he_class" should be present
+ 		Then element having xpath ".//*[@id='hiddenElement']" should be present
+
+ 	Scenario: verify checkbox checked or not
+
+ 		Then checkbox having id "chk1" should be checked
+ 		Then checkbox having name "chk5_name" should be checked
+ 		Then checkbox having xpath ".//*[@id='chk1']" should be checked
+ 		Then checkbox having class "chk5_class" should be checked
+ 		
+ 		Then checkbox having id "chk2" should be unchecked
+ 		Then checkbox having name "chk3_name" should be unchecked
+ 		Then checkbox having class "chk4_class" should be unchecked
+
+	Scenario: verify checkbox checked or not - negative test 1
+		
+		Then checkbox having class "chk3_class" should be checked
+
+	Scenario: verify checkbox checked or not - negative test 2
+		
+		Then checkbox having class "chk5_class" should be unchecked
+
+ 	Scenario: verify radio button selected or not
+
+ 		Then radio button having id "rdb1" should be selected
+ 		Then radio button having id "rdb2" should be unselected
+
+	Scenario: verify radio button selected or not - negative test 1
+
+ 		Then radio button having id "rdb2" should be selected
+
+	Scenario: verify radio button selected or not - negative test 2
+
+ 		Then radio button having id "rdb1" should be unselected
+
+	Scenario: verify link present or not
+
+ 		Then link having text "selenium-cucumber gem" should be present
+		Then link having text "xyz" should not be present
+
+	Scenario: verify pop-up alert text
+		
+		When I click on element having id "try_it"
+ 		Then I should see alert text as "Press a button!"
+		Then I accept alert 
+	
+	Scenario: verify image by id
+		Then actual image having id "img1" and expected image having id "img1" should be similar
+
+	Scenario: verify image by xpath
+		Then actual image having xpath ".//*[@id='img1']" and expected image having xpath ".//*[@id='img1']" should be similar
+
+	Scenario: verify image by id and path - negative test 1
+		Then actual image having id "img1" and expected image having path "C:/dropshadow-flower-pink.png" should be similar
+
+ 	Scenario: verify image by path - negative test 2
+		Then actual image having path "http://shared.ooyala.com.s3.amazonaws.com/dropshadow-flower-pink.png" and expected image having path "C:/dropshadow-flower-pink.png" should be similar
+
+	

data/Example/features/click_steps_Ex.feature

@@ -0,0 +1,28 @@
+
+Feature: Click On Elements
+        As a user I should able to click on elements
+ 
+ 	Scenario: Open test page 
+
+		Given I open test page
+ 		
+	Scenario: click on elements
+ 	
+ 		Then I enter "selenium-cucumber" into input field having id "f_name"
+		Then I click on element having id "reset"
+		Then element having id "f_name" should have attribute "value" with value ""
+		
+	Scenario: double click on elements
+		
+		Then I double click on element having id "dbClick"
+		Then element having name "demo2_name" should be present
+	
+	Scenario: click on links having text
+	
+		Then I click on link having text "selenium-cucumber gem"
+		Then I should see page title as "selenium-cucumber | RubyGems.org | your community gem host"
+		
+	Scenario: click on links having partial text
+
+		Then I click on link having partial text "Home"
+		Then I should see page title as "Selenium-Cucumber | Code Less… Test More…"

data/Example/features/configuration_step_Ex.feature

@@ -0,0 +1,9 @@
+
+Feature: Configuration Printing Step
+        As a user I should able to print configuration
+ 
+ 	Scenario: Print Configuration
+ 	
+        Given I print configuration
+ 		Given I open test page
+   

data/Example/features/input_steps_Ex.feature

@@ -0,0 +1,87 @@
+
+Feature: Input Step
+        As a user I should able to give inputs
+ 
+ 	Scenario: Open test page
+ 	
+ 		Given I open test page
+ 	
+ 	Scenario: Enter text into textfield
+ 	
+ 		Then I enter "abc" into input field having id "f_name"
+ 		Then element having id "f_name" should have attribute "value" with value "abc"
+
+ 		Then I enter "xyz" into input field having name "lname_name"
+ 		Then element having name "lname_name" should have attribute "value" with value "xyz"
+
+		Then I enter "pqr" into input field having class "address_class"
+ 		Then element having class "address_class" should have attribute "value" with value "pqr"
+
+
+	Scenario: Clear text From textfield
+
+		Then I clear input field having id "f_name"
+		Then element having id "f_name" should have attribute "value" with value ""
+ 		
+		Then I clear input field having name "lname_name"
+		Then element having name "lname_name" should have attribute "value" with value ""
+ 		
+ 		Then I clear input field having class "address_class"
+		Then element having class "address_class" should have attribute "value" with value ""
+ 		
+	Scenario: select option from dropdown list
+ 		
+ 		Then I select "Select_5" option by text from dropdown having id "dropdownList1"
+ 		Then option "Select_5" by text from dropdown having id "dropdownList1" should be selected
+
+		Then I select 1 option by index from dropdown having id "dropdownList1"
+		Then option "Select_1" by text from dropdown having id "dropdownList1" should be selected
+
+		Then I select "s3" option by value from dropdown having id "dropdownList1"
+		Then option "s3" by value from dropdown having id "dropdownList1" should be selected
+ 	
+ 	Scenario: select option from Multiselect List
+ 		
+ 		Then I select "Volvo" option by text from multiselect dropdown having name "cars"
+		Then I select 4 option by index from multiselect dropdown having name "cars"
+		Then I select "opel" option by value from multiselect dropdown having name "cars"
+		
+	Scenario: unselect all options from Multiselect List
+		
+		Then I unselect all options from multiselect dropdown having name "cars"
+
+	Scenario: select all options from Multiselect List
+
+		Then I select all options from multiselect dropdown having name "cars"
+ 		
+ 	Scenario: selecting checkbox
+ 		
+ 		Then I check the checkbox having id "chk3"
+ 		Then checkbox having id "chk3" should be checked
+
+		Then I check the checkbox having name "chk2_name"
+ 		Then checkbox having name "chk2_name" should be checked
+ 		
+ 	Scenario: unselecting checkbox
+
+		Then I uncheck the checkbox having class "chk5_class"
+		Then checkbox having class "chk5_class" should be unchecked
+
+	Scenario: toggle checkbox		
+
+		Then I toggle checkbox having id "chk4"
+		Then checkbox having id "chk4" should be checked
+		
+		Then I toggle checkbox having id "chk4"
+		Then checkbox having id "chk4" should be unchecked
+
+	Scenario: selecting radio buttons
+ 		
+ 		Then I select radio button having id "rdb2"
+ 		Then radio button having id "rdb2" should be selected
+
+ 		Then I select radio button having name "rdb3_name"
+ 		Then radio button having name "rdb3_name" should be selected
+
+ 		Then I select radio button having class "rdb4_class"
+		Then radio button having class "rdb4_class" should be selected 		

data/Example/features/javascript_steps_Ex.feature

@@ -0,0 +1,19 @@
+
+Feature: Javasciprt Handling Steps
+        As a user I should able to handle javascript pop-up 
+
+	Scenario: Open test page
+ 		Given I open test page 
+ 	
+ 	Scenario: accept alert
+
+ 		Then I click on element having id "try_it"
+ 		Then I accept alert 
+       	Then element having id "demo" should have text as "You pressed OK!"
+
+	Scenario: dismiss alert       	
+	
+       	Then I click on element having id "try_it"
+ 		Then I dismiss alert
+ 		Then element having id "demo" should have text as "You pressed Cancel!"
+		

data/Example/features/navigation_steps_Ex.feature

@@ -0,0 +1,45 @@
+Feature: Navigation Steps 
+        As a user I should able to navigate on web page
+ 
+ 	Scenario: Open test page
+ 		Given I open test page
+
+ 	Scenario: navigating back/forward and refresh page
+ 		
+ 		Then I click on link having text "selenium-cucumber gem"
+ 		Then I should see page title as "selenium-cucumber | RubyGems.org | your community gem host"
+
+ 		Then I navigate back
+		Then I should see page title as "Test Page for selenium-cucumber"	
+
+ 		Then I navigate forward
+ 		Then I should see page title as "selenium-cucumber | RubyGems.org | your community gem host"
+
+ 		Then I navigate back
+ 		Then I should see page title as "Test Page for selenium-cucumber"	
+		
+ 		Then I refresh page
+ 		Then I should see page title as "Test Page for selenium-cucumber"	
+		
+
+	Scenario: Zoom in/out web page
+		
+ 		Then I zoom in page
+ 		Then I zoom out page
+		Then I reset page view
+
+	Scenario: Scroll web page
+		
+		Then I scroll to element having id "demo"
+		Then I scroll to top of page
+    	Then I scroll to end of page
+
+	Scenario: Hover over elelment
+		
+		Then I hover over element having xpath "html/body/fieldset[8]/p/a[1]"
+		
+	Scenario: Interacting with browser
+		
+		Then I resize browser window size to width 400 and height 400
+		Then I maximize browser window
+		#Then I close browser

data/Example/features/new.feature

@@ -0,0 +1,7 @@
+Feature: Assertion Steps
+        As a user I should able to verify using assert steps
+ 
+ 	Scenario: Open test page
+ 		Given I open test page
+
+	

data/Example/features/progress_step_Ex.feature

@@ -0,0 +1,18 @@
+
+Feature: Progress Steps
+        As a user I should able to wait
+ 
+ 	Scenario: Open test page
+ 		Given I open test page
+
+ 	Scenario: wait for elements to display
+ 		
+ 		Then element having id "hiddenElement" should not be present
+		Then I wait 15 seconds for element having id "hiddenElement" to display
+ 		Then element having id "hiddenElement" should be present
+
+	Scenario: wait for elements to enabled
+
+ 		Then element having id "disabledBt" should be disabled
+ 		Then I wait 15 seconds for element having id "disabledBt" to enable
+ 		Then element having id "disabledBt" should be enabled

data/Example/features/screenshot_step_Ex.feature

@@ -0,0 +1,11 @@
+
+Feature: Screenshot Step
+        As a user I should able to take screenshot
+ 
+ 	Scenario: Open test page
+ 		
+ 		Given I open test page
+
+ 	Scenario: take screenshot
+ 	
+ 		Then I take screenshot

data/Example/features/step_definitions/custom_steps.rb

@@ -0,0 +1,14 @@
+require 'selenium-cucumber'
+
+# Do Not Remove This File
+# Add your custom steps here
+# $driver is instance of webdriver use this instance to write your custom code
+
+
+
+Given(/^I open test page$/) do
+	link = 'file:///'
+  	link+= File.absolute_path("test_page.html")
+  	navigate_to(link) 
+end
+

data/Example/features/support/env.rb

@@ -0,0 +1,38 @@
+require 'rubygems'
+require 'selenium-webdriver'
+
+def print_error
+  puts "\nInappropraite browser \"#{ENV['BROWSER']}\""
+  puts "\nUsage : cucumber BROWSER=browser_name"
+  puts "\nbrowser_name can be one of following :"
+  puts "1.ie\n2.chrome\n3.ff\n4.safari\n5.opera" 
+  puts "\nNow using default browser \"Firefox\""
+end
+
+case ENV['BROWSER']
+  when 'ie'
+    browser_type = :ie
+  when 'ff'
+    browser_type = :ff
+  when 'chrome'
+    browser_type = :chrome
+  when 'opera'
+    browser_type = :opera
+  when 'safari'
+    browser_type = :safari
+  else
+    if ENV['BROWSER']
+      print_error
+    end
+    browser_type = :ff
+end
+
+
+begin
+    $driver = Selenium::WebDriver.for(browser_type)
+    $driver.manage().window().maximize()
+
+  rescue Exception => e
+    puts e.message
+end
+

data/Example/features/support/hooks.rb

@@ -0,0 +1,34 @@
+#Cucumber provides a number of hooks which allow us to run blocks at various points in the Cucumber test cycle
+
+Before do
+  # Do something before each scenario.
+end
+
+Before do |scenario|
+  # The +scenario+ argument is optional, but if you use it, you can get the title,
+  # description, or name (title + description) of the scenario that is about to be
+  # executed.
+end
+
+After do |scenario|
+  # Do something after each scenario.
+  # The +scenario+ argument is optional, but
+  # if you use it, you can inspect status with
+  # the #failed?, #passed? and #exception methods.
+
+  if(scenario.failed?)
+    #Do something if scenario fails.
+  end
+end
+
+#Tagged hooks
+
+Before('@Ex_tag1, @Ex_tag2') do
+  # This will only run before scenarios tagged
+  # with @cucumis OR @sativus.
+end
+
+AfterStep('@Ex_tag1, @Ex_tag2') do
+  # This will only run after steps within scenarios tagged
+  # with @cucumis AND @sativus.
+end