.sds-sidebar{color:#fff;}

Make Your Tests Saucey - Running Selenium Tests Against Multiple Platforms and Browsers

Jul 24, 2017 7:51:00 AM / by Ashley Hope posted in Agile Testing, Ruby, BDD, TDD, Testing, Selenium, ATDD, SauceLabs, Modernized Technology

5 Comments

Cucumber, Selenium and Gherkin have become popular tools for helping teams implement test automation or what is often referred to as Acceptance Test Driven Development (ATDD) or Behavior Driven Development (BDD). By running your tests locally, you can ensure your application runs as expected on your OS/Browser setup, but to truly know that the app works on other configurations, you need a way to emulate numerous environments. SauceLabs is a web service that you can sign up to which will give the ability to test on many OS/Browser setups, including numerous mobile options.

In this article, we will cover:

  1. Why Use SauceLabs?
  2. Connecting Your Tests to SauceLabs
  3. Parameterize your Rake File to Pass in Platform and Browser
  4. Using a Secure Tunnel to Access Your Internal Application

In this article series we use Ruby as the implementation language (and we recommend Ruby when there is no other existing preference). However, these examples will translate easily to other languages like Java. 

If you are not familiar with Selenium, Cucumber and Gherkin take a look at our related introductory blog "The 5 Step Guide for Selenium, Cucumber, and Gherkin" and "Rake Up and Optimize Your Tests"

Read More

Rake Up and Optimize Your Automated Tests

Jul 21, 2017 8:48:00 AM / by Ashley Hope posted in Agile Testing, Cucumber, Automated Testing, BDD, Testing, Selenium, ATDD, Rake, Modernized Technology

1 Comment


Cucumber, Selenium and Gherkin have become popular tools for helping teams implement test automation or what is often referred to as Acceptance Test Driven Development (ATDD) or Behavior Driven Development (BDD). As you grow your test suite and as it becomes larger and more complex, you may find your test project becomes bloated and messy. This article will lay out steps you can take to optimize your test organization and ways to provide unmeasured flexibility in running different tests on different browsers.

In this article, we will cover:

  1. 'Tagging' Tests for better organization
  2. 'Hook' up your tests with @Before and @After hooks
  3. 'Support' your test organization with the Support folder
  4. 'Rake' up your cucumber statements with a Rakefile

In this article series we use Ruby as the implementation language (and we recommend Ruby when there is no other existing preference). However, these examples will translate easily to other languages like Java.

If you are not familiar with Selenium, Cucumber and Gherkin take a look at our related introductory blog  "The 5 Step Guide for Selenium, Cucumber, and Gherkin" and "Getting the Most out of Cucumber, Gherkin, and Selenium"
Read More

Getting the most out of Cucumber, Gherkin and Selenium

Apr 27, 2017 3:29:00 PM / by Eric Taylor posted in Cucumber, Gherkin, Automated Testing, BDD, Testing, Selenium, ATDD, Modernized Technology

1 Comment

 

Cucumber, Selenium and Gherkin have become popular tools for helping teams implement test automation or what is often referred to as Acceptance Test Driver Development (ATDD) or Behavior Driven Development (BDD).  In this article we will cover some more advanced features of the Gherkin language that can help you write tests that are simpler and more reusable.

We will cover:

  1. Using Regular Expressions for Dynamic Data
  2. Scenario Outlines
  3. Tables as Arguments
  4. Backgrounds

In this article series we use Ruby as the implementation language (and we recommend Ruby when there is no other existing preference). However, these examples will translate easily to other languages like Java.

 

Read More

Advanced Selenium: Multiple Browsers and Environments

Mar 28, 2017 2:11:05 AM / by Eric Taylor posted in Agile Testing, Ruby, Cucumber, Automated Testing, BDD, Testing, Selenium, ATDD, WebDriver, Browser, Modernized Technology

0 Comments

Cucumber, Selenium and Gherkin have become popular tools for helping teams implement test automation - what is often referred to as Acceptance Test Driver Development (ATDD) or Behavior Driven Development (BDD).  In this article we will cover some more advanced features of Selenium and Cucumber and show how to environmentalize your test framework so you can run the same tests against different environments or browsers.  In this article series, we use Ruby as the implementation language (and we recommend Ruby when there is no other existing preference). However, these examples will translate easily to other languages like Java. 

If you are not familiar with Selenium, Cucumber and Gherkin take a look at our related introductory blog "The 5 Step Guide for Selenium, Cucumber, and Gherkin".

Read More

The 5 Step Guide for Selenium, Cucumber, and Gherkin

Aug 22, 2016 8:00:00 AM / by Eric Taylor posted in Ruby, Cucumber, Gherkin, Automated Testing, BDD, Selenium, ATDD, Modernized Technology

30 Comments

Increasingly, IT development organizations are turning to automated testing techniques to improve the quality of their code and to save time and money. While this market remains fractured, Selenium, Cucumber, and Gherkin have become quite popular and are increasingly the frameworks of choice for user interface and integration test automation.

This guide is intended for someone who is not familiar with Selenium, Cucumber, Gherkin and would like to get started. We will go through the installation of the framework, describe how the technologies work together, and then write a few tests.

Through this guide you will install and use the following:

  • Ruby (2.3.3 or higher)
  • Selenium Webdriver (3.2.1) 
  • Cucumber (2.4.0)
  • Gherkin (4.1.1)
  • Text Editor or IDE (SublimeText, Atom, Notepad++, Eclipse)
  • Firefox 

Platforms Covered:

  • Mac OS X
  • Windows

NOTE: As of the latest update of this blog on March 21, 2017 we suggest you use Selenium Webdriver 3.2.1 and not a newer version since the newer versions of Selenium Webdriver are incompatible with Firefox.

Read More

7 Signs Your Architecture Is Not Agile-Ready

Jul 19, 2016 7:58:14 AM / by Eric Taylor posted in Automated Testing, TDD, Unit Testing, ATDD, Architecture, Modernized Technology

0 Comments

I have heard it asked many times, “Where do architects fit into Agile?” But that's the wrong question.  Instead, you should be asking, "Is our architecture Agile-Ready?"

One reason for adopting Agile is to enable “flow” to breakout – meaning your organization accelerates moving business needs from the concept phase to delivering customer value in production. Agile, grounded in Lean principals, asks your teams to look at everything that does not contribute to “flow” as waste and to eliminate it. But what if your application architecture is holding you back? 

Read More

Subscribe to Email Updates

Lists by Topic

see all