druid-s 1.0.0

data/Rakefile

@@ -0,0 +1,33 @@
+require 'rubygems'
+require 'bundler'
+require 'rspec/core/rake_task'
+require 'cucumber'
+require 'cucumber/rake/task'
+
+RSpec::Core::RakeTask.new(:spec) do |spec|
+  spec.ruby_opts = "-I lib:spec"
+  spec.pattern = 'spec/**/*_spec.rb'
+end
+
+namespace :spec do
+  RSpec::Core::RakeTask.new(:html) do |spec|
+    spec.ruby_opts = "-I lib:spec"
+    spec.pattern = 'spec/**/*_spec.rb'
+    spec.rspec_opts = "--format html --out #{ENV["SPEC_REPORT"] || "specs.html"}"
+  end
+end
+
+task :spec
+
+task :lib do
+  $LOAD_PATH.unshift(File.expand_xpath("lib", File.dirname(__FILE__)))
+end
+
+task :default => :spec
+
+
+namespace :features do
+  Cucumber::Rake::Task.new(:watir, "Run features with Watir webdriver") do |t|
+    t.profile = "watir"
+  end
+end

data/cucumber.yml

@@ -0,0 +1,6 @@
+<%
+std_opts = "--no-source --color --format pretty"
+%>
+
+default: DRIVER=WATIR <%= std_opts %>
+watir: DRIVER=WATIR <%= std_opts %>

data/druid.gemspec

@@ -0,0 +1,30 @@
+# -*- encoding: utf-8 -*-
+$:.push File.expand_path("../lib", __FILE__)
+require "druid/version"
+
+Gem::Specification.new do |s|
+  s.name = "druid-s"
+  s.platform = Gem::Platform::RUBY
+  s.version = Druid::VERSION
+  s.date = '2024-01-16'
+  s.authors = ["Amber Yuan"]
+  s.homepage = "https://github.com/amber-yuan/druid-s"
+  s.summary = %q{Druid DSL for browser testing}
+  s.description = %q{Druid DSL that works with Watir}
+  s.license = 'MIT'
+  s.files = `git ls-files -z`.split("\x0").reject { |f| f.match(%r{^(pkg|spec|features|coverage)/})}
+  s.files = `git ls-files`.split("\n")
+  s.test_files = `git ls-files -- {test,spec,features}/*`.split("\n")
+  s.executables = `git ls-files -- bin/*`.split("\n").map{ |f| File.basename(f)}
+  s.require_paths = ["lib"]
+  s.add_dependency "watir", "~> 7.3.0"
+
+  s.add_development_dependency "rspec", "~> 3.10"
+  s.add_development_dependency "cucumber", "~> 9.0"
+  s.add_development_dependency "net-http-persistent", "~> 4.0"
+  s.add_development_dependency 'rack', '~> 3.0'
+  s.add_development_dependency 'rackup', '~> 2.1'
+
+  s.add_runtime_dependency 'page_navigation', '~> 0.10'
+
+end

data/features/area.feature

@@ -0,0 +1,33 @@
+Feature: Area
+
+  Background:
+    Given I am on the static elements page
+
+  Scenario: Retrieve an area element
+    When I retrieve the area element
+    Then I should know it exists
+    And I should know it is visible
+
+  Scenario Outline: Locating areas on the page
+    When I search for the area by "<search_by>"
+    Then I should be able to click the area
+
+  Examples:
+    | search_by |
+    | id        |
+    | class     |
+    | xpath     |
+    | index     |
+    | css       |
+
+  Scenario: Getting the coordinates for the area
+    When I retrieve the area element
+    Then I should see the coordinates are "0,0,82,126"
+
+  Scenario: Getting the shape for the area
+    When I retrieve the area element
+    Then I should see the shape are "rect"
+
+  Scenario: Getting the href from the area
+    When I retrieve the area element
+    Then I should see the href is "sun.html"

data/features/async.feature

@@ -0,0 +1,16 @@
+Feature: Handling Asynch calls
+
+  Background:
+    Given I am on the async elements page
+
+  Scenario: Click a button when it is visible
+    When I make the button invisible
+    Then I should be able to click it when it becomes visible
+
+  Scenario: Wait until something is not visible
+    Then I should be able to wait until the button becomes invisible
+
+  Scenario: Wait for an element to disappear from the page
+    When I add a button a few seconds from now
+    And I remove a button a few seconds from now
+    Then I should not be able to find the button

data/features/audio.feature

@@ -0,0 +1,61 @@
+Feature: Support for the audio element
+
+  Background:
+    Given I am on the audio video page
+
+  Scenario: Finding an audio element
+    When I retrieve the audio element from the page
+    Then I should know it exists
+    And I should know it is visible
+
+  Scenario Outline: Locating an audio element on the page
+    When I search for the audio element by "<search_by>"
+    Then I should know it is visible
+
+    Examples:
+      | search_by   |
+      | id          |
+      | class       |
+      | xpath       |
+      | index       |
+      | css         |
+
+  Scenario Outline: Locating audios using multiple parameters
+    When I search for the audio element by "<param1>" and "<param2>"
+    Then I should know it is visible
+
+    Examples:
+      | param1  | param2  |
+      | class   | index   |
+
+  Scenario: Should know if it is autoplay
+    When I retrieve the audio element from the page
+    Then I should know the audio is not autoplay
+
+  Scenario: Should know if the controls are displayed
+    When I retrieve the audio element from the page
+    Then I should know that the controls are displayed
+
+  Scenario: Should know if it is paused
+    When I retrieve the audio element from the page
+    Then I should know that the audio is paused
+
+  Scenario: Should know its volume
+    When I retrieve the audio element from the page
+    Then I should know that its volume is 1
+
+  Scenario: Should know if it has ended
+    When I retrieve the audio element from the page
+    Then I should know that it has not ended
+
+  Scenario: Should know if it is seeking
+    When I retrieve the audio element from the page
+    Then I should know that it is not seeking
+
+  Scenario: Should know if it is in a loop
+    When I retrieve the audio element from the page
+    Then I should know that it is not in a loop
+
+  Scenario: Should know if it is muted
+    When I retrieve the audio element from the page
+    Then I should know that it is muted

data/features/bold.feature

@@ -0,0 +1,20 @@
+Feature: Bold
+
+  Background:
+    Given I am on the static elements page
+
+  Scenario: Getting the text of headings
+    When I get the bold text for the "b" element
+    Then I should see "some text in bold" in bold
+
+  Scenario Outline: Locating b on the page
+    When I search bold text for the b by "<search_by>"
+    Then I should see "some text in bold" in bold
+
+  Examples:
+  | search_by |
+  | id        |
+  | class     |
+  | xpath     |
+  | index     |
+  | css       |

data/features/button.feature

@@ -0,0 +1,81 @@
+Feature: Button
+  In order to interact with buttons
+  Testers will need access and interrogation ability
+
+  Background:
+    Given I am on the static elements page
+
+  Scenario: Clicking a button (type=submit)
+    When I click the button
+    Then I should be on the success page
+
+  Scenario: Clicking a button (type=image)
+    When I click the button with type image
+    Then I should be on the success page
+
+  Scenario: Clicking an image button by src
+    When I click the image button using src
+    Then I should be on the success page
+
+  Scenario: Clicking an image button by alt
+    When I click the image button using alt
+    Then I should be on the success page
+
+  @name
+  Scenario Outline: Locating buttons on the page
+    When I locate the button by "<locate_by>"
+    Then I should be able to click the button
+
+    Examples:
+    | locate_by |
+    | id        |
+    | class     |
+    | name      |
+    | xpath     |
+    | index     |
+    | text      |
+    | value     |
+    | css       |
+
+  Scenario Outline: Locating real buttons on the page
+    When I locate the button by "<locate_by>"
+    Then I should be able to click the real button
+
+    Examples:
+    | locate_by |
+    | id        |
+    | class     |
+    | name      |
+    | index     |
+    | value     |
+
+  Scenario: Retrieve a button element
+    When I retrieve a button element
+    Then I should know it exists
+    And I should know it is visible
+
+  @multi
+  Scenario Outline: Locating button using multiple parameters
+    When I search for the button by "<param1>" and "<param2>"
+    Then I should be able to click the button
+
+    Examples:
+    | param1  | param2  |
+    | class   | index   |
+    | name    | index   |
+
+  @multi
+  Scenario Outline: Locating real button using multiple parameters
+    When I search for the button by "<param1>" and "<param2>"
+    Then I should be able to click the real button
+
+    Examples:
+    | param1  | param2  |
+    | class   | index   |
+    | name    | index   |
+
+  @locator
+  Scenario: Finding a button dynamically
+    When I find a button while the script is executing
+    Then I should see that the button exists
+    And I should be able to click the button element

data/features/canvas.feature

@@ -0,0 +1,34 @@
+Feature: Support for the canvas element
+
+    Background:
+      Given I am on the static elements page
+
+    Scenario: Retrieve a canvas element
+      When I retrieve the canvas element
+      Then I should know it exists
+      And I should know it is visible
+
+    Scenario Outline: Locating a canvas on the page
+      When I search for the canvas by "<search_by>"
+      Then I should know it is visible
+
+      Examples:
+        | search_by   |
+        | id          |
+        | class       |
+        | xpath       |
+        | index       |
+        | css         |
+
+    Scenario: Determining the width and height of the canvas
+      When I retrieve the canvas element
+      Then I should see that the canvas width is "200"
+      And I should see that the canvas height is "100"
+
+    Scenario Outline: Locating canvases using multiple parameters
+      When I search for the canvas element by "<param1>" and "<param2>"
+      Then I should know it is visible
+
+      Examples:
+        | param1  | param2  |
+        | class   | index   |

data/features/checkbox.feature

@@ -0,0 +1,48 @@
+Feature: Check Box
+  In order to interact with check boxes
+  Testers will need access and interrogation ability
+
+  Background:
+    Given I am on the static elements page
+
+  Scenario: Selecting a checkbox
+    When I select the First check box
+    Then the First check box should be selected
+    When I unselect the First check box
+    Then the First check box should not be selected
+
+  Scenario Outline: Locating check boxes on the page
+    When I locate the check box by "<locate_by>"
+    Then I should be able to check the check box
+
+    Examples:
+    | locate_by |
+    | id        |
+    | class     |
+    | name      |
+    | xpath     |
+    | index     |
+    | value     |
+    | label     |
+    | css       |
+
+  Scenario: Retrieve a CheckBox
+    When I retrieve a check box element
+    Then I should know it exists
+    And I should know it is visible
+
+  @multi
+  Scenario Outline: Locating check boxes using multiple paramters
+    When I search for the check box by "<param1>" and "<param2>"
+    Then I should be able to check the check box
+
+    Examples:
+    | param1  | param2  |
+    | class   | index   |
+    | name    | index   |
+
+  @locator
+  Scenario: Finding a check box dynamically
+    When I select the first check box while the script is executing
+    Then I should see that the checkbox exists
+    And the First check box should be selected

data/features/div.feature

@@ -0,0 +1,45 @@
+Feature: Div
+  In order to interact with divs
+  Testers will need access and interrogation ability
+
+  Background:
+    Given I am on the static elements page
+
+  Scenario: Getting the text from a div
+    When I get the text from the div
+    Then the text should be "page-object rocks!"
+
+  @name
+  Scenario Outline: Locating divs on the page
+    When I locate the div by "<locate_by>"
+    Then the text should be "page-object rocks!"
+
+    Examples:
+    | locate_by |
+    | id        |
+    | class     |
+    | xpath     |
+    | index     |
+    | text      |
+    | title     |
+    | css       |
+
+  Scenario: Getting the div element
+    When I retrieve the div element
+    Then I should know it exists
+    And I should know it is visible
+
+  @multi
+  Scenario Outline: locating divs using multiple parameters
+    When I search for the div by "<param1>" and "<param2>"
+    Then the text should be "page-object rocks!"
+
+    Examples:
+    | param1  | param2  |
+    | class   | index   |
+
+  @locator
+  Scenario: Finding a div dynamically
+    When I get the text from a div while the script is executing
+    Then I should see that the div exists
+    And the text should be "page-object rocks!"