Janet Gregory presents Current Testing Challenges with SoftTest Ireland
Upcoming SlideShare
Loading in...5
×
 

Janet Gregory presents Current Testing Challenges with SoftTest Ireland

on

  • 859 views

Visit www.softtest.ie for more information about Irish Software Testing.

Visit www.softtest.ie for more information about Irish Software Testing.

Statistics

Views

Total Views
859
Views on SlideShare
661
Embed Views
198

Actions

Likes
0
Downloads
14
Comments
0

1 Embed 198

http://softtest.ie 198

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

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

    Janet Gregory presents Current Testing Challenges with SoftTest Ireland Janet Gregory presents Current Testing Challenges with SoftTest Ireland Presentation Transcript

    • September 2012 Belfast & DublinJanet Gregory, DragonFire Inc. Copyright 2012
    • First agile team – 2000 Currently – coaching, testing Book – Agile Testing; January 2009Copyright 2012DragonFire Inc. 2
    • • challenges • testing activities • automation ◦ the pyramid ◦ where it falls apart • collaborative solutionsCopyright 2012DragonFire Inc. 3
    • • mixed messages by thought leaders • technology • distributed teams • organization cultureCopyright 2012DragonFire Inc. 4
    • Testing activities
    • Automate at the feature levelpushthe Automate at the storytests levellower Automate at the task level
    • Tests / Examples passes toAPI teststructure Test Method / Fixture calls Developer CodeCopyright 2012DragonFire Inc.
    • TestLogIn test / examplesUser Name Password Expected result commentsJanetGregory Password Access system as JanetGregory Valid combo savedJanet Gregory Password Error Space in user name boolean TestLogIn (userName, password, expected result) call LogIn (userName, password) compare (actual result, expected result) if true, return pass test method else / fixture return fail end boolean LogIn (name,pwd) Developer code stuff ……….. code if logged in, return true else return false Copyright 2012 DragonFire Inc. end
    • • enables testers / • tests are usually business to define tests through the UI• test code can be in • programmers aren’t programming language usually willing to help• programmers can run • tests are implemented tests as they code after the code is written• testers can ask • testers create and programmers for help implement all tests• takes time from ‘coding’ production codeCopyright 2012DragonFire Inc. 9
    • • less abstraction between layers ◦ presentation vs. business layer • more logic in the GUI layer • where is the separation in tests? • who does what?Copyright 2012DragonFire Inc. 10
    • • JavaScript• Flash• Flex• Ajax• Cross-browser compatibility• Mobile
    • So, if we can’t test all (most) functionality at the API layer ... Any stories to share?Copyright 2012DragonFire Inc. 12
    • • ATDD (acceptance test driven development) through the GUI ◦ Jasmine: BDD framework to test JavaScript ◦ Sebium: Fit and Selenium combined (Cirilo Wortel) ◦ Selenium: possible, but harder ◦ Ruby / Watir: possible, but harder• Unit tests ◦ jQuery Copyright 2012 DragonFire Inc. 13
    • two big questions .... Do testers need to know how to code? Can programmers do all the testing? 14
    • • system architecture ◦ high level (context) ◦ component levelThx to Lynn McKee for the term technical awareness 15
    • for example, • in JavaScript, there is a small, but important issue with the parseInt function, used to transform strings to integers. • the issue arises when we create a Date object from a yyyy-mm-dd string. Could your testers and programmers have a conversation about this?Copyright 2012DragonFire Inc. 16
    • Copyright 2012DragonFire Inc. 17
    • Brian Marick
    • • slicing stories • ATDD (acceptance test driven development) • sharing technical details • teaching testing skills • learning test patterns • learning / teaching design techniques • creating test harnesses, mocks, stubsCopyright 2012DragonFire Inc. 19
    • Copyright 2012DragonFire Inc. 20
    • Instead of saying NO, or being the gatekeeper Be the information provider so business can make the decisionsQuestions?Copyright 2012DragonFire Inc. 21
    • • agile-testing@yahoogroups.com • www.lisacrispin.com • http://gojko.net/2010/10/05/rethinking-user-interface-test- automation/ • http://net.tutsplus.com/tutorials/javascript-ajax/testing-your- javascript-with-jasmine • http://www.software-testing.com.au/blog/2011/01/25/test- automation-styles-and-alternatives-to-the-page-object- pattern/ • www.qualityperspectives.caCopyright 2012DragonFire Inc. 22
    • Contact Information janet@agiletester.ca www.janetgregory.ca twitter: @janetgregoryca lisa@agiletester.ca www.lisacrispin.com twitter: @lisacrispin www.agiletester.caCopyright 2012DragonFire Inc.