• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
Functional & Performance Test Automation with CI
 

Functional & Performance Test Automation with CI

on

  • 2,828 views

Testers entering the Agile domain are no longer on the other side of the wall. Without the wall, the developer playground of CI is a testing smorgasbord. As an Agile Tester there are many ways to ...

Testers entering the Agile domain are no longer on the other side of the wall. Without the wall, the developer playground of CI is a testing smorgasbord. As an Agile Tester there are many ways to consider how to design and execute automated tests and continuously keep the pulse on quality of the builds. However when it comes to leveraging existing CI pipeline for functional and performance tests many testers may not realize that main ingredients are already built-in. This presentation will share the recipes on how to propel functional and performance automated tests with immediate test results feedback to the entire team with your existent CI engine.
Presentation is base on:
• Hudson/Jenkins CI engine
• Ruby and Rake to setup, execute and tear-down test environments
• Hpricot (Ruby gem) and Hudson plug-ins to report and trend graphical results dynamically

Statistics

Views

Total Views
2,828
Views on SlideShare
2,816
Embed Views
12

Actions

Likes
1
Downloads
0
Comments
0

3 Embeds 12

http://www.linkedin.com 9
https://www.linkedin.com 2
http://www.slideshare.net 1

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment
  • View from live dev-cam – remote members dial in for standup and this is what they see.Here’s the rest of the room – we are powered by the arc – Friday afternoon furniture re-arranging resulted in some powerful fengshui – seems to help the flow of communicationStart video at 1:45http://dl.dropbox.com/u/22563350/CIMG0491.mp4
  • JoEllenSwitching CI is not a big deal thanks to modular approach
  • JoEllenBuild pipeline consists of multiple, coupled builds…first build is triggered by checkinEach build after the first one is triggered by the successful completion of the previous build.Failing build means the end of the pipe for that check in..and we get to hear our wonderful build-break audio
  • LeonardElaborate on types of tests outside of CIMention previous experience as QA - Leonard’s personal experience from the past – did it the hard way Java w. DB Silo’d
  • JoEllenVisible w/o going somewhere else;Visible to remote team membersUniform/generic presentation of results & readily accessible to everyone (no permissions etc)
  • LeonardRake runs the install in the test environmentRake shells out to mstest to execute the testJenkins saves artifacts and produces reportJenkins
  • JoEllen
  • Leonard
  • JoEllen
  • LeonardTake another with all green
  • LeonardAdd more screenshots – screenshot test; formatted report with pass/fail info, trend plugin for p/f over time
  • JoellenAdd more screenshots – screenshot test; formatted report with pass/fail info, trend plugin for p/f over time
  • LeonardUsing Jenkins Performance Trending Plug-inRuby gem to xForm the XML  display data for trending & charting

Functional & Performance Test Automation with CI Functional & Performance Test Automation with CI Presentation Transcript

  • Flex Your Testing Automation Muscles with Development CI
     
    Leonard Fingerman (leonard.fingerman@versionone.com), Agile Tester
  • Words of Wisdom
    “Continuous Integration doesn't get rid of bugs, but it does make them dramatically easier to find and remove” (Martin Fowler)
  • Our Team
    8 developers
    3 product owners
    2 testers
    1 designer
  • Our Product (not a sales pitch)
  • Our CI Tools
    CruiseControl-> Team City -> Hudson -> Jenkins
    Modular CI pipeline approach is key
    Well-supported source control system (e.g. Git)
    CI de-coupled build tool(s) (e.g. Ruby/Rake)
  • CI –DEV Pipeline
  • CI, the Automated Testing Platform…
    • Typically CI is in the developer domain
    • Testers can and should exploit CI environment for earlier defect detection
  • CI, the Automated Testing Platform…
    Scheduling tasks is built-in
    Run-time environments can be setup and torn down via build tasks (e.g. Ruby Rakefiles)
    Reporting & trending is available via plug-ins
    Notification is built-in
    Visible to the entire team
  • CI - Testing Pipeline
    CI – Dev pipeline  .exe
  • Build Setup
    Jenkins makes it easy
  • What’s Rake ?
    A simple Ruby build tool similar to make
    Rakefiles (rake‘s version of Makefiles) defined in standard Ruby syntax. No XML files to edit. No quirky Makefile syntax to worry about
    Can specify tasks with dependencies
    A well-defined library of tasks to make creating rakefiles easier
  • Rake Examples
  • Testing Dashboard
  • Jenkins Project page
  • Artifacts
  • Performance Test Trending (Jenkins plugin)
  • Questions ?
    JoEllen Carter (joellen.carter@versionone.com)
    Leonard Fingerman (leonard.fingerman @versionone.com