lapis_lazuli 2.0.1 → 3.0.0

data/lib/lapis_lazuli/generators/cucumber/template/config/config.yml

@@ -24,39 +24,24 @@ error_strings:
 ################################################################################
 # Environment specific variables
 test:
+  root: http://username:password@test.spritecloud.com #Not an existing page, note the username/password user inside the URL
   pages:
-    root: http://username:password@test.spritecloud.com #Not an existing page, note the username/password user inside the URL
     home: /
     about-us: /about-us/
 
 uat:
+  root: http://username:password@uat.spritecloud.com #Not an existing page, note the username/password user inside the URL
   pages:
-    root: http://username:password@uat.spritecloud.com #Not an existing page, note the username/password user inside the URL
     home: /
     about-us: /about-us/
 
 production:
+  root: https://www.spritecloud.com
   pages:
-    root: https://www.spritecloud.com
     home: /
     about-us: /about-us/
     testing: /testing/
     blog: /blog/
-    functional-testing: /testing/functional/
-  training-page: http://training-page.testautomation.info
-
-
-# Different user variables
-users:
-  default-user: # These are the default variable settings. If no setting was specified, these values will be used.
-    username: test
-    password: test
-    gender: 'Male'
-    experience: 'Ruby,Cucumber,HTML,XPath'
-    biography: 'Hello, I am Gijs, I am a Test Engineer for spriteCloud and I like to be lazy and let machines do my work'
-  random-user: # In ./features/support/functions.rb '_RAND-ALPHA_' is replaces for random alphanumeric characters.
-    username: usr_RAND-ALPHA_
-    password: test_RAND_
-    gender: 'Female'
-    experience: 'Ruby,Gherkin'
-    biography: 'Hello, I am a randomized user, today is _TIMESTAMP_ seconds after the existance of computers'
+    functional-testing: /testing/functional-testing/
+    jobs: /jobs
+    training-page: http://training-page.testautomation.info/#

data/lib/lapis_lazuli/generators/cucumber/template/config/cucumber.yml

@@ -3,9 +3,8 @@
 # Generated by LapisLazuli, version <%= config[:lapis_lazuli][:version] %>
 # Author: "<%= config[:user] %>" <<%= config[:email] %>>
 #
-# Ask developer of testsuite to add profiles where desired.
-# This file defines predefined profiles that can be used.
-# Example > Cucumber -t @homepage -p default -p localhost
+# Cucumber profiles are used to group certain tags and variables
+# This way you can run specific scenario's on specific environments.
 
 <%% timestamp = Time.now.strftime("%Y%m%d_%H%M") %>
 
@@ -17,19 +16,49 @@ html_report: -f pretty -f html --out=results/<%%=timestamp%>_report.html
 junit_report: -f pretty -f junit --out=results
 
 ################################################################################
-# Supported browsers (default = firefox)
+# Supported browsers (default = chrome)
+chrome: BROWSER=chrome
 ff: BROWSER=firefox
 firefox: BROWSER=firefox
-chrome: BROWSER=chrome
-ie: BROWSER=ie
-safari: BROWSER=safari
-edge: BROWSER=edge
-
 
 ################################################################################
 # Listed environments (default is set in config.yml)
-t: TEST_ENV=test -t @t,@test
-test: TEST_ENV=test -t @t,@test
+t: -p test
+test: TEST_ENV=test -t '@t or @test or @all_env or @all_environments' -t 'not @disabled_on_test'
+# When you run cucumber -p t
+# 1. t: -p test > will call profile `test`
+# 2. TEST_ENV=test > Sets a ruby variable ENV['TEST_ENV'] = 'test'
+# 3. '@t or @test or @all_env or @all_environments' > Runs all features / scenario's that include either one of these tags
+# 4. -t 'not @disabled_on_test' > Will not run any feature / scenario that includes this that
+# A scenario including '@test @disabled_on_test', will be ignored!
+
+a: -p acceptance
+acc: -p acceptance
+accpetance: TEST_ENV=acceptance -t '@a or @acceptance or @all_env or @all_environments' -t 'not @disabled_on_acceptance' -t 'not @disabled_on_acc'
+
+p: -p production
+prod: -p production
+production: TEST_ENV=production -t '@p or @prod or @production or @all_env or @all_environments' -t 'not @disabled_on_production' -t 'not @disabled_on_prod'
+
+################################################################################
+# The following is another exmaple of creating (and combining) profiles. In this one we use Version. But it could be anything really.
+# With version profile you can easily combine a certain environment with a version
+# An then include (or exclude) certain scenario's that are only available on a specific version.
+# E.G.: bundle exec cucucumber -p acceptance -p version_14
+
+v_12: -p version_12
+version_12: VERSION=12 -t '@v_12 or @ver_12 or @version_12 or @all_versions' -t 'not @disabled_on_ver_12' -t 'not @disabled_on_version_12'
+
+v_14: -p version_14
+version_14: VERSION=14 -t '@v_14 or @ver_14 or @version_14 or @all_versions' -t 'not @disabled_on_ver_14' -t 'not @disabled_on_version_14'
 
-p: TEST_ENV=production -t @p,@prod
-production: TEST_ENV=production -t @p,@prod
+################################################################################
+# A few example cucumber commands you could execute:
+# Run all acceptance tests
+# bundle exec cucumber -p acc
+#
+# Only test a specific scenario on production
+# bundle exec cucumber -p prod -t @login
+#
+# Use the default environment set in config.yml and run a specific tag with extended output
+# bundle exec cucumber -t @test_24 -x

data/lib/lapis_lazuli/generators/cucumber/template/config/users.yml

@@ -0,0 +1,21 @@
+---
+users:
+  default-user: # See ./features/helpers/user_helper.rb
+    username: ta_RAND-ALPHA_
+    password: Ab!2_RAND_
+    gender: male
+    experience: Ruby,Gherkin
+    biography: This is the default test user
+    complete_all: 1
+  production:
+    test-user:
+      username: test
+      password: test
+  test:
+    test-user:
+      username: ta-test-user
+      password: ^%8jah7hH
+  uat:
+    test-user:
+      username: ta-uat-user
+      password: (87hsjaJH#

data/lib/lapis_lazuli/generators/cucumber/template/features/1_basic.feature

@@ -0,0 +1,49 @@
+@basic @all_env
+Feature: Example Feature
+When I want to learn how to make test cases
+As a user of the test automation tool
+I want to run and adjust the tests below
+
+  @basic_01
+  Scenario: example01 - Spritecloud search
+    Given the user navigates to "blog"
+    When the user searches for "lapis lazuli"
+    Then text "Open Source" should display somewhere on the page
+
+  @basic_02
+  Scenario: example02 - scrolling down
+    Given the user navigates to "home"
+    When the user scrolls down
+    Then text "Project-based services are typically short-term" should display somewhere on the page
+
+  @basic_03
+  Scenario: example03 - Going to a search result
+    Given the user navigates to "https://www.spritecloud.com/?s=lapis+lazuli"
+    When the user scrolls down
+    And the user clicks on link "/announcing-lapislazuli/"
+    Then text "A few days later you are working" should display somewhere on the page
+
+  @basic_04
+  Scenario Outline: example04 - checking multiple pages for the logo
+    Given the user navigates to "<page>"
+    When the user clicks on the spritecloud logo
+    Then the user should be on page "home"
+    Scenarios:
+      | page               |
+      | blog               |
+      | home               |
+      | about-us           |
+      | testing            |
+      | functional-testing |
+
+  ### LEARNING TO DEBUG ###
+  # Scenario' or Feature's including the tag @dev will be ingored when running a regular profile. To run this do:
+  # bundle exec cucumber -t @basic_04 -p debug
+  # or, if you want to test it on a specific environment:
+  # bundle exec cucumber -p production -p debug -t @basic_04
+  # Good luck fixing the problems!
+  @basic_05 @dev
+  Scenario: example_05 - confirming there is a no results page
+    Given the user navigates to "blog"
+    When the user searches for "no_results_expected"
+    Then the text "Nothing Found" should display on the blog page

data/lib/lapis_lazuli/generators/cucumber/template/features/2_account.feature

@@ -0,0 +1,38 @@
+@account @all_env
+Feature: User accounts
+  This feature will make sure the user account functionality is working as expected
+  By checking registration, login and logout functionality
+
+  # This is a best practise example. Please note the following
+  # By defining a register, log-in and log-out state, we can easily re-use all these preconditions
+  # All the scenario's aren't completed, but it should be easy to implement it into your own project.
+
+  @account_01 @log_in #@pause # You can add @pause to have a break between every step.
+  Scenario: account_01 - Logging in
+    Given the user is logged out
+    When "test-user" logs in
+    Then the page should display as logged in state
+
+  @account_02 @log_out
+  Scenario: account_02 - Logging out
+    Given "test-user" is logged in
+    When the user clicks on the logout button
+    Then the page should display as logged out state
+
+  @account_03
+  Scenario: account_03 - Opening the registration form
+    Given the user is logged out
+    When the user clicks on the registration button
+    Then the registration form should display
+
+  @account_04
+  Scenario: account_04 - Successful registration
+    Given "default-user" has the registration form opened
+    When the user completes registration
+    Then the successful registration message should display
+
+  @account_05
+  Scenario: account_05 - Logging in a new registration
+    Given "default-user" has registered a new account
+    When the user logs in
+    Then the page should display as logged in state

data/lib/lapis_lazuli/generators/cucumber/template/features/3_todo_list.feature

@@ -0,0 +1,23 @@
+@todo @all_env
+Feature: Todo list
+  In this feature we will test the todo functionality
+  We do this by adding, completing and deleting the todo lists'
+
+  @todo_01
+  Scenario: todo_01 - adding a todo item
+    Given "test-user" is logged in
+    When a todo item with text "Hello world" is added
+    Then a todo item with text "Hello world" should be present
+
+  @todo_02
+  Scenario: todo_02 - removing all todo items
+    Given "test-user" has at least 1 todo item
+    When the user marks all todo items as completed
+    And the clear completed button is pressed
+    Then no todo items should display
+
+  @todo_03
+  Scenario: todo_03 - confirming the progress bar
+    Given "test-user" has exactly 8 todo items
+    When the user marks 4 todo items as completed
+    Then the progress bar should display at 50 percent

data/lib/lapis_lazuli/generators/cucumber/template/features/helpers/authentication_helper.rb

@@ -0,0 +1,122 @@
+module Auth
+  # This is the Authentication helper, it will have all functions to log in, log out or ensure one of these statusses.
+  # For every part of functionality of a project, you can create a new helper, to keep your TA organised.
+  extend LapisLazuli
+  class << self
+
+    @@user = ''
+    @login_page = 'training-page'
+
+    # This is a list of elements relevant for this helper.
+    # The following is short notation, *only* use this if the element selector can be done in 1 line.
+    # @formatter:off
+    def form_container; browser.wait(:like => [:form, :id, 'form-login']); end
+    def username_field; form_container.input(:xpath => '//*[@id="login-username"]'); end
+    def password_field; form_container.input(:id => 'login-password'); end
+    def login_button; browser.button(:id => 'button-login'); end
+    # @formatter:on
+
+    # Following elements that need more advanced options/search patterns
+    def logged_in_element(timeout=10, throw=true)
+      browser.wait(
+        :like => [:a, :id, 'user_dropdown'],
+        :timeout => timeout,
+        :throw => throw
+      )
+    end
+
+    def logged_out_element(timeout=10, throw=true)
+      browser.wait(
+        :like => [:form, :id, 'form-login'],
+        :timeout => timeout,
+        :throw => throw
+      )
+    end
+
+    # Next are the functions called from the step definitions
+    # `ensure_something` is best practise to be used for functions that should get the test to a certain state. For example:
+    # `ensure_log_out` only logs out if you're logged in
+    # `log_out` will blindly try to log out and fail if you're already logged out
+    def ensure_log_out
+      Nav.to('training-page')
+      if Auth.is_logged_in?
+        Auth.log_out
+        if Auth.is_logged_in?
+          error 'Page did not display in logged out state after logging out'
+        end
+      end
+    end
+
+    # Makes sure that a specific user is logged in, if it's not already.
+    def ensure_log_in(user='default-user')
+      Nav.to('training-page')
+      unless Auth.is_logged_in?(user)
+        # If the wrong user is logged in, we should ensure a log out action and then log in again
+        Auth.ensure_log_out
+        Auth.log_in(user)
+        # Double check if the login was successful, if not, throw an error.
+        unless Auth.is_logged_in?(user)
+          error "Failed to log in `#{user}`."
+        end
+      end
+    end
+
+    # If user=nil, any logged in user is acceptable, else we want to make sure the username matches with the logged in user.
+    def is_logged_in?(user=nil)
+      # For performance, we do a 0 second wait for the logged_out_element
+      if Auth.logged_out_element(0, false)
+        return false
+      end
+      login_elm = Auth.logged_in_element(5, false)
+      if login_elm.nil?
+        # Logged in element not found, check if the logged out element is present
+        logout_elm = Auth.logged_out_element(0, false)
+        if logout_elm.nil?
+          # Neither of the elements were present, this should not be possible.
+          error 'Failed to find the logged_out element and the logged_in element. The user is not logged in, nor logged out.'
+        else
+          # Logged out element was found the second time.
+          return false
+        end
+      else
+        # The logged in element was found, should we match the username?
+        if user.nil?
+          # No, any user is fine
+          return true
+        else
+          # Yes, load the user data and match the username
+          User.load_user_data(user)
+          return login_elm.span(:class => ['username', 'ng-binding']).text == User.get('username')
+        end
+      end
+    end
+
+    def log_out
+      Auth.logged_in_element.click
+      dropdown = browser.wait(:like => [:ul, :class, 'dropdown-menu'])
+      browser.find(
+        :like => [:a, :id, 'link-logout'],
+        :context => dropdown
+      ).click
+    end
+
+    def log_in(user=nil, renew_session=false)
+      # If user=nil, we expect that there already is user data loaded in a previous step.
+      User.load_user_data(user) unless user.nil?
+
+      Auth.username_field.to_subtype.to_subtype.set(User.get('username'))
+      Auth.password_field.to_subtype.to_subtype.set(User.get('password'))
+      Auth.login_button.click
+
+      unless Auth.is_logged_in? user
+        alert = browser.find(:like => [:div, :class, 'alert'], :throw => false)
+        if alert.nil?
+          error "Failed to log in user #{user}"
+        else
+          alert.flash
+          error "Found error while logging in #{user}: `#{alert.html}`"
+        end
+      end
+    end
+  end
+end

data/lib/lapis_lazuli/generators/cucumber/template/features/helpers/navigation_helper.rb

@@ -0,0 +1,64 @@
+# Simple helper that makes navigating using the config file easier
+# It will check if a given string is a URL or a config value and goto that page accordingly
+module Nav
+  extend LapisLazuli
+  class << self
+
+    # Navigates to a given URL or page.url configuration if the current URL is not the same
+    # Then confirms that the new URL is loaded.
+    def to(config_page_or_url, force_refresh = false)
+      url = self.set_url(config_page_or_url)
+      browser.goto url unless url == browser.url and !force_refresh
+      Nav.wait_for_url url
+    end
+
+    # Waits until the browser URL is the same as the given URL
+    def wait_for_url(url)
+      browser.wait_until(timeout: 5, message: "URL did not become `#{url}`") {
+        browser.url.include? url
+      }
+    end
+
+    # Loads the URL from the config, prioritized from top to bottom:
+    # production.pages.home
+    # production.pages.home.path
+    # pages.home
+    # pages.home.path
+    def get_url page
+      begin
+        return env_or_config("pages.#{page}")
+      rescue RuntimeError
+        return env_or_config("pages.#{page}.path")
+      end
+    end
+
+    # Confirms if the given URL is a valid URL
+    def is_url? string
+      uri = URI.parse(string)
+      %w( http https ).include?(uri.scheme)
+    rescue URI::BadURIError
+      false
+    rescue URI::InvalidURIError
+      false
+    end
+
+    # returns the expected URL
+    def set_url(config_page_or_url)
+      if Nav.is_url? config_page_or_url
+        # Return the given URL if it alreadt is a valid URL
+        return config_page_or_url
+      else
+        # Look for the URL in the config files
+        path_or_url = get_url config_page_or_url
+        if Nav.is_url? path_or_url
+          # If it is a URL now, then return it
+          return path_or_url
+        else
+          # Else add an expected 'root' to the path.
+          return env('root') + path_or_url
+        end
+      end
+    end
+
+  end
+end

data/lib/lapis_lazuli/generators/cucumber/template/features/helpers/registration_helper.rb

@@ -0,0 +1,102 @@
+module Register
+
+  extend LapisLazuli
+  class << self
+
+    # This is a list of elements relevant for this helper.
+    # The following is short notation, *only* use this if the element selector can be done in 1 line.
+    # @formatter:off
+    def form; browser.wait(:like => [:form, :id, 'form-register']); end
+    def open_register_button; browser.find(:like => [:button, :id, 'button-register']); end
+    def username_field; browser.wait(:element => {:name => 'username'}, :context => Register.form); end
+    def password_field; browser.find(:element => {:name => 'password'}, :context => Register.form); end
+    def experience_field; browser.find(:like => [:select, :id, "register-experience"], :context => form); end
+    def biography_field; browser.find(:like => [:textarea, :id, 'register-bio']); end
+    def policy_checkbox; browser.find(:like => [:input, :id, 'register-complete-all']) end
+    def submit_button; browser.find(:button => {:id => 'button-save'}, :context => Register.form); end
+    # @formatter:on
+
+    def gender_radio(gender)
+      browser.find(
+        :label => {:text => /#{gender}/i},
+        :context => Register.form,
+        :message => "Unable to find gender `#{gender}`, are you sure it's an option to select?"
+      )
+    end
+
+    def select_experiences(*experience_list)
+      experience_list.each do |exp|
+        option = browser.find(
+          :option => {:value => /#{exp}/i},
+          :context => Register.experience_field
+        )
+        option.click(:control)
+      end
+    end
+
+    # The following 3 functions are a typical example of something to use.
+    # First a function in which you perform an action (open_something, click_something, press_something)
+    def open_registration
+      Register.open_register_button.click
+    end
+
+    # Second, a function that confirms that the action was successful
+    def is_registration_open?
+      return Register.form rescue false
+    end
+
+    # And finally as function that ensures an action was successfully completed.
+    def ensure_open_registrarion
+      Auth.ensure_log_out
+      Register.open_registration unless Register.is_registration_open?
+    end
+
+    def fill_form
+      #the setter goes too fast sometimes not finishing the username, this will re-set the username when it does
+      browser.wait_until(timeout: 10, message: 'False did not become true withing 10 seconds') {
+        Register.username_field.to_subtype.set(User.get('username'))
+        Register.username_field.value == User.get('username')
+       }
+      Register.username_field.to_subtype.set(User.get('username'))
+      Register.password_field.to_subtype.set(User.get('password'))
+      Register.gender_radio(User.get('gender')).click
+      Register.select_experiences(User.get('experience').split(','))
+      Register.biography_field.to_subtype.set(User.get('biography'))
+      Register.policy_checkbox.to_subtype.set((User.get('complete_all').to_i == 1))
+    end
+
+    def submit_form
+      Register.submit_button.click
+      browser.wait(
+        :like => [:div, :class, 'modal-backdrop fade in'],
+        :condition => :while
+      )
+    end
+
+    def register_user
+      Register.fill_form
+      Register.submit_form
+    end
+
+    def registration_result
+      alert = browser.wait(like: [:div, :class, 'alert'], timeout: 2, throw: false)
+      if alert.nil?
+        return false, 'No message was displayed after registering'
+      elsif !alert.html.include? User.get('username')
+        return false, "An error message did display, but didn't contain the expected text: `#{alert.html}`"
+      end
+      return true, 'Successfully found the success message'
+    end
+
+    def ensure_registered(user)
+      begin
+        Auth.ensure_log_in(user)
+        Auth.log_out
+      rescue Exception => e
+        Register.ensure_open_registrarion
+        Register.register_user
+      end
+    end
+
+  end
+end