.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

4 Essential Skills for a QA Engineer in an Agile Environment - Modernized Technology & Testing

Aug 8, 2016 1:56:25 PM / by Sanjay Zalavadia posted in DevOps, Agile, Agile Testing, Zephyr, Automated Testing, Quality Assurance, Testing, Modernized Technology

0 Comments


Teams are an intricate balance of skills, cooperation, leadership and willingness to go the extra mile to make a quality product. Each grouping has individuals with specific roles and responsibilities, as well as a chain of command to help guide the team to success. Within a testing team, the QA Engineer plays an integral part that helps testing run smoothly and ensures that all projects are thoroughly evaluated.

Although the QA Engineer isn't the top dog in the team, he or she does report to the QA Manager. The person in the QA Engineer role essentially takes the requirements and test strategies and generates test plans. But that's not all. These individuals also execute these tests, leverage QA testing tools to report issues and analyze test results to mitigate problems and create better tests. This is obviously an important position to be in, but many don't fully understand what capabilities are needed. Let's take a look at some of the essential skill requirements for a QA engineer:

  • Communication
  • Product Understanding
  • Coding and Creativity
  • Automation
Read More

Subscribe to Email Updates

Lists by Topic

see all