A one pager on automated checks

I was asked to summarise the process for automated checks in an easily readable format for non techies to understand, so heres a little snippet of what I can share:

A pragmatic approach to automated testing is taken.  Automating only where we see the value.

Testing layers

There are multiple layers of automated checks:

  • Unit – Run on every check in.  Check individual units of code. When code is checked in these tests are run and if any fail are fixed.   
  • Integration – Run overnight. Check where Enactor talks to other systems, e.g the database.
  • UI – Run overnight.  Follow a user journey, simulating button clicks and typing as if it was a real user.  

 

Manual to Automated

Scenarios are creating using Behaviour Driven Development (BDD) format for every user story.  A scenario is worded in the Gherkin language.  e.g.Given When Then 

These are output as Cucumber feature files, which can then be automated using Selenium Webdriver, using Java code
References

Cucumber  https://en.wikipedia.org/wiki/Cucumber_(software)

Selenium webdriver http://www.seleniumhq.org/projects/webdriver/

BDD – https://en.wikipedia.org/wiki/Behavior-driven_development

 

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s