DEVELOPER  BLOG

 

 

 

 

Creating Data-Driven Functional Tests with LiquidTest

 

Mark Bayazit

 

 

 

 

 

Websites and web-applications have become technically complex, leading to a need for advanced automated test scripts that can validate their functionality. These scripts typically “walk through” a specific process and check to make sure certain actions and objects operate as expected. As the user provides different input into these web-applications, they change their behavior or present different datasets, prompts, or error messages, so it is not enough to simply run scripts with one set of values. Instead, the script needs to be able to run many different iterations of the same test, each with a different set of values. The ability to take actions (like entering text, choosing a radio-button, clicking a link, or validating returned content) dynamically is called parameterization, and a test that does this is often referred to as a “parameterized” or “data-driven” test. Read more..

 

 

These icons link to social bookmarking sites where readers can share and discover new web pages.
  • Digg
  • del.icio.us
  • StumbleUpon
  • Reddit
  • DZone
  • TwitThis
  • email
  Comments (0)

 

 


 

 

 

 

About this blog..

 

This is an informal place for the team at JadeLiquid to discuss software, the rotation of the earth and other things usually discussed in the JadeLiquid corridors.

 

 

 

Subscribe: By Feed  By Email

 

 

 

 

 

Categories

 

 

JadeLiquid

LiquidTest

 

 

Software Testing

 

 

WebRenderer

 

 

 

 

Recent Posts

 

 

Setting up LiquidTest with Maven
Knowing your Enemy - Foundations of LiquidTest
Eclipse and LiquidTest UI Introduction
Testing Dynamic Elements – Having a Plan B
Setting up LiquidTest with Subversion and Hudson (Continuous Integration) part 2

 

 

 

 

 

Popular Posts

 

 

Testing complex Ajax content
One tool to rule them all - Reducing team division
Protecting investment: Tests that do not break with page changes
Creating Data-Driven Functional Tests with LiquidTest
Setting up LiquidTest with Subversion and Hudson (Continuous Integration) - part 1
Is manual testing crippling your development project?
Setting up LiquidTest with Subversion and Hudson (Continuous Integration) part 2
Testing Dynamic Elements – Having a Plan B
Eclipse and LiquidTest UI Introduction
Knowing your Enemy - Foundations of LiquidTest

 

 

 

 

 

Archives

 

 

March 2010 (1) February 2010 (1) November 2009 (1) October 2009 (1) September 2009 (2) August 2009 (1) July 2009 (1) June 2009 (1) April 2009 (1) March 2009 (1)

 

 

 

 

 
   News / Events

 

 > LiquidTest Release 1.0.18 - Available Now!
 > Automate your Dev/Test Process - Webinar
 > LiquidTest Best Practices - Webinar
 > Next Generation Agile Testing - Webinar
 > Is manual testing crippling your project? - Blog
 > Reducing team division - Blog
 > Testing complex Ajax content - Blog
 
 
   Recently Added Content  
 
 > Setting up LiquidTest with Maven - Blog
 > Knowing your Enemy - Blog
 > Eclipse and LiquidTest UI Introduction - Blog
 > Testing Dynamic Elements: Having a Plan B - Blog
 > Setting up LiquidTest with SVN and Hudson - Blog
 > Creating Data-Driven Functional Tests - Blog
 > Reducing Test Maintenance - Blog
 
 
  Copyright JadeLiquid Software - 2010