blog

Let's talk about testing

Standard platform, operating system and browser recommendations (October 18)

This entry is part 16 of 16 in the series Standard Platform, Operating System and Browser Recommendations

Introduction

The following post updates our recommendations for platforms, operating systems and browsers to use when testing commercial web sites targeting consumers in Europe.

Our recommendations are based on usage figures widely available on the Internet, our experience and our analysis of client needs. Since browser versions change frequently, we review and update these recommendations regularly.

Continue Reading »

Standard platform, operating system and browser recommendations (July 18)

This entry is part 15 of 16 in the series Standard Platform, Operating System and Browser Recommendations

Introduction

The following post updates our recommendations for platforms, operating systems and browsers to use when testing commercial web sites targeting consumers in Europe.

Our recommendations are based on usage figures widely available on the Internet, our experience and our analysis of client needs. Since browser versions change frequently, we review and update these recommendations regularly.

Continue Reading »

Standard platform, operating system and browser recommendations (April 18)

This entry is part 14 of 16 in the series Standard Platform, Operating System and Browser Recommendations

Introduction

The following post updates our recommendations for platforms, operating systems and browsers to use when testing commercial web sites targeting consumers in Europe.

Our recommendations are based on usage figures widely available on the Internet, our experience and our analysis of client needs. Since browser versions change frequently, we review and update these recommendations regularly.

Continue Reading »

The 3 most common mistakes writing Gherkin features

In the past I’ve worked on many projects where they either used Gherkin to describe functionality or to be used for test automation. The following recommendations are useful for both usages.

common gherkin mistakes

1. Writing scripts in first person instead of third person

When starting with Gherkin, people quickly feel like they should describe the actions they are performing when going trough a functionality.

Wrong

Given I am logged in
When I delete a post on the blog
Then I should see a successful deleted message

The problem with the case above is that it’s not clear who this “I” person is. Is it an administrator, a moderator or a member? This is quite important information when reading Gherkin, so you can understand it quicker. This post goes more in-depth about why third person is better.

Right

Given the administrator is logged in
When the user deletes a post on the blog
Then a successful deleted message should display

2. Describing every action instead of a functionality

When writing Gherkin, it’s often seen as if you have to describe every action to get to the next step: Every click, every text input, web-page. But Gherkin is meant to describe a specific flow you’re going trough.

Wrong

Given the user is on "http://training-page.testautomation.info/"
When the user fills in "test" for username
And the user fills in "test" for password
And the user clicks on the login button
And the user clicks on the logout button
Then the user should be on the login page
And the avatar should not display in the right top

Right

Given the test user is logged in on the training page
When the user logs out
Then the login page should display as expected

When this scenario is used in functional testing, someone reading it will understand what is suppose to happen.

For test automation all the different clicks can be solved on a code level. Also, with the more functional description, it’s easier to group the code and repeat yourself less.

3. Using absolute values instead of configurable values

When writing Gherkin scripts, it’s always quick and easy to simply use the absolute values that you want to use. For example a username and password, or the values used in a registration form.

It’s best practise to move your absolute values to a configuration file, so you can set user information in a central place.

Wrong

Given the user navigates to "http://training-page.testautomation.info/"
When the user fills in "test" for "#login-username"
And the user fills in "test" for "#login-password"
And the user clicks on button "submit"
Then the page should display in logged in state

Right

Given "test-user" navigates to page "landing-page"
When the user logs in
Then the page should display in logged in state

So in this case the URL is moved into a configuration value called “landing-page” and the user credentials in “test-user”. If at any point in the future one of these values change, you’ll only have to change one configuration value with it.

Final word

When writing Gherkin scenario’s, ask yourself the following:

  • What is the goal of my scenario?
  • Is my scenario descriptive?
  • Can I use less steps to describe it?

Thanks for reading! – Gijs Pauldies, Test Automation Engineer

Standard platform, operating system and browser recommendations (December 17)

This entry is part 13 of 16 in the series Standard Platform, Operating System and Browser Recommendations

Introduction

The following post updates our recommendations for platforms, operating systems and browsers to use when testing commercial web sites targeting consumers in Europe.

Our recommendations are based on usage figures widely available on the Internet, our experience, and our analysis of client needs. Since browser versions change frequently, we review and update these recommendations regularly.

Continue Reading »

5 best practices for ecommerce testing during the holiday season

Black Friday and Cyber Monday have just passed for 2017, with online businesses continuing the annual trend of conquering more of the global market. This is a pretty predictable result, and highlights the need for retailers to make sure their ecommerce website is performing at optimal levels during the holiday season.

We’ve tested A LOT of ecommerce webshops over the years, so our team knows what they are talking about it when it comes to best practice. Here are some recommendations I collected from them about how best to prepare for a holiday deployment.

Continue Reading »

Set up and run your Cucumber and Selenium web tests on Gitlab-CI within minutes

Build great software faster! CI/CD is hot and is still gaining interest. Test Automation is obviously essential within any Continuous Integration setup in order to get test feedback often and fast. Within the test automation groups here at spriteCloud we have seen a lot of different setups. We have been integrating test automation into CI tools such as Jenkins, TeamCity, Travis, TFS, Circle CI, Bamboo and Gitlab. Out of all the solutions we are a big fan of Gitlab, especially since it is making the integration of test automation a breeze.

Continue Reading »

Getting to know: Loes Besters, our newest Software Test Engineer

spriteCloud has welcomed many new people to the team these past few months, and Loes is our newest addition. She is joining us as a Junior Software Test Engineer after a career break, and is excited to get back into the world of testing. Read on to find about more about her.

Continue Reading »

Complete Setup Guide for Ruby, Cucumber and Watir on Windows (2017)

Introduction

Our last post on installing Ruby, Cucumber and Watir was written in 2015. But since then, things have changed and software has been updated, so it’s time for another update!

Continue Reading »

VR Days Europe 2017: what’s happening in the VR industry?

Viewing virtual reality from a developer’s perspective is one thing, but looking at it from a tester’s viewpoint is something else altogether. This is what we aimed to talk about at VR Days this year. Last year we proudly sponsored the event and members of our team went as visitors to enjoy the conference and exhibition, but this year we jumped right in and rented a booth at the Exhibition. Located in a prime spot in De Kromhouthal in Amsterdam Noord, our VR testing team were active participants and had some informative, thought-provoking conversations with VR developers from all industries.

Our main aim? Talk about VR testing and make it available to as many people as possible. Here’s what we found.

Continue Reading »

Reputation. Meet spriteCloud

Find out today why startups, SMBs, enterprises, brands, digital agencies, e-commerce, and mobile clients turn to spriteCloud to help improve their customer experiences. And their reputation. With complete range of QA services, we provide a full service that includes test planning, functional testing, test automation, performance testing, consultancy, mobile testing, and security testing. We even have a test lab — open to all our clients to use — with a full range of devices and platforms.

Discover how our process can boost your reputation.

We use cookies to give you the best browsing experience possible. For more information, please read our cookie policy.

The cookie settings on this website are set to "allow cookies" to give you the best browsing experience possible. If you continue to use this website without changing your cookie settings or you click "Accept" below then you are consenting to this.

Close