Session 

 

Presented by: 

Marcus  R  

  

Brought to you by: 

  

340 Corporate Way, Suite   Orange Park, FL 32073 888‐2

W11 Concurrent4/9/2014   2:00 PM     

“Getting Started with Open Source  Testing Tools” 

 

  Merrell

etailMeNot, Inc.  

    

300,68‐8770 ∙ 904‐278‐0524 ∙ sqeinfo@sqe.com ∙ www.sqe.com 

Marcus Merrell RetailMeNot, Inc  

A test architect at RetailMeNot, Inc., Marcus Merrell has written UI and API test frameworks for several products since 2001. Marcus is obsessed with code design and holds sacred the philosophy that test frameworks should be approached, developed, and tested just as carefully as the production software they seek to examine. The successful demonstration of these principles has led to an intense focus on collaboration between testers and developers, and to a deep appreciation for code that is at once simple and sophisticated―an API for testers which is reusable, interface-agnostic, and universal to many problem sets.

Getting Started with Open Source Testing ToolsMarcus Merrell, RetailMeNot, inc

@mmerrell

What You Need in a Framework

Multiple browsersAbility to build a “model”Simple execution

CICommand-line

Robust reportingExtensibilityBeware of “codeless” solutions

ChoicesRuby (RSpec, Riot)Python (pytest, nose)Java (JUnit, TestNG)PHP (PHPUnit)… or the thing I’m going to talk about

Our FrameworkContains all the tools above, plus several more

ProxyDatabase interactionAnalytics

Not open source just yetWe’re looking for partners

Tech StackMavenSpringTestNGSeleniumHibernateCQMS

FeaturesScalability

Autoscaling Grid!Data-driven tests

AnalyticsOutclicksSite Catalyst

Database ValidationTest data creation

HierarchyPagesElementsTests

…let’s just look at some code

ExecutionTeamCity kicks off Maven job, which executes TestNG tests

ReportingTeamCityDatabaseTestRails…extensible, can be used with anything

Statistics500 RetailMeNot core tests300 test for mobile site450 internal admin tests100 tests for Native iOS app800 headless API tests

DownsideCommunity supported, but this can be an upside in many casesCan be difficult to measure costsCan be difficult to get started

(that’s where we want to help!)Requires higher skill level to navigate

ConclusionOpen source = robust, well-supported, tight controlScalable, particularly from a license point of viewIf you choose well-supported projects, you’ll get what you need