04/10/23 14:37

EDS and the EDS logo are registered trademarks of Electronic Data Systems Corporation. EDS and the EDS logo are registered trademarks of Electronic Data Systems Corporation. EDS is an equal opportunity employer and values the diversity ofEDS is an equal opportunity employer and values the diversity ofits people. © 2005 Electronic Data Systems Corporation. All rights reserved. its people. © 2005 Electronic Data Systems Corporation. All rights reserved.

Agile TestingAgile TestingTest Early, Test Often, Test Fast

Sharon Picken - EDS

Test Early, Test Often, Test Fast

Sharon Picken - EDS

Page 2© 2005 Electronic Data Systems Corporation. All rights reserved.© 2005 Electronic Data Systems Corporation. All rights reserved.

Agile ApproachesAgile Approaches

• eXtreme Programming (XP) – “test-driven development”

• Scrum

• Agile Rational Unified Process (Agile RUP)

• Improve team productivity and overall development quality

• Must be considered in the context of a broader methodology framework

• Key success factors are team collaboration, metrics and core lifecycle management tools

Refer to “Best Practices for Agile Development”, Liz Barnett and Uttam Narsu, Refer to “Best Practices for Agile Development”, Liz Barnett and Uttam Narsu, © © Giga Research 2003Giga Research 2003

Page 3© 2005 Electronic Data Systems Corporation. All rights reserved.© 2005 Electronic Data Systems Corporation. All rights reserved.

Foundations of Agile TestingFoundations of Agile Testing

Process

EnvironmentPeople

Tools

Page 4© 2005 Electronic Data Systems Corporation. All rights reserved.© 2005 Electronic Data Systems Corporation. All rights reserved.

An Agile ClientAn Agile Client

• Empowered to make funding and scope decisions

• Participated on a regular basis with developers and testers

• Enthusiastic supporter of new approach (Agile RUP)

• Exercised admin level control over development and test environments

• Changed project direction in a timely manner when necessary

Page 5© 2005 Electronic Data Systems Corporation. All rights reserved.© 2005 Electronic Data Systems Corporation. All rights reserved.

• Technical Architecture (TA) Pilot

• Highly visible J2EE application architecture pilot covering “most used” business functions

• Small (< 15 people) co-located collaborative team of Architects, BAs, Developers, Testers

• Not delivering critical business processes into Production – medium risk project

• Risk-based architectural and functional requirements baselines – Risks and Use Cases

• Iterative development and testing of successive application architecture builds - RUP

• Demonstrated business value from the initial build – high risks addressed early

Page 5

An Agile ProjectAn Agile Project

Page 6© 2005 Electronic Data Systems Corporation. All rights reserved.© 2005 Electronic Data Systems Corporation. All rights reserved.

Test Early – The Testing V–ModelTest Early – The Testing V–Model

Create TestProcedures

Identif y TestCases

Dev elop TestScenarios

Prepare TestStrategy

DesignDocuments

DesignDocuments

FunctionalSpecif ication

RequirementsDocument

DefineRequirements

Analysis /Functional Design

ArchitecturalDesign

Detailed TechnicalDesign

Construction

Performance &Acceptance

Testing

System Testing

Validates

OptionalSy stem Test

Integration Testing

Unit Testing

Release Control

Test P

lannin

g &

Initia

lT

est C

ase

Deve

lopm

ent

Time Static Testing Dynamic Testing

Test

Case

/Data

Deve

lopm

ent

& E

xecu

tion

ControlledEnv ironment

Validates

Validates

Validates

Did I Build the System Right?

Did I Build the Right System?

Page 7© 2005 Electronic Data Systems Corporation. All rights reserved.© 2005 Electronic Data Systems Corporation. All rights reserved.

Test Types – IBM-Rational FURPS+Test Types – IBM-Rational FURPS+

QUALITY

DIMENSIONS

Functionality

Re

liab

ility

Supportability

Human Factors

Page 8© 2005 Electronic Data Systems Corporation. All rights reserved.© 2005 Electronic Data Systems Corporation. All rights reserved.

Test Often - Test Environments and LevelsTest Often - Test Environments and Levels

Test Environment

Sy

ste

m T

es

t

Bu

ild

Ac

ce

pta

nc

e T

es

t

Inte

gra

tio

n T

es

t

Ac

ce

pta

nc

e T

es

t

Development Environment

Un

it (C

om

po

ne

nt)

Te

st

Inte

gra

tio

n T

es

t

Release

Page 9© 2005 Electronic Data Systems Corporation. All rights reserved.© 2005 Electronic Data Systems Corporation. All rights reserved.

TA Pilot Test EnvironmentTA Pilot Test Environment

Page 10© 2005 Electronic Data Systems Corporation. All rights reserved.© 2005 Electronic Data Systems Corporation. All rights reserved.

TA Pilot Test Automation ArchitectureTA Pilot Test Automation Architecture

Rational RequisitePro

RequisitePro Project- TA Pilot.rsp

MS SQL Server

Rational Project- TAPilotRAProject.rsp

Rational ClearQuest

cqmaster.dbf (schema)

/ dbms / ORACLE / ITIP_DEVTAPIL

cquser.dbf (user)

ClearQuest Project- TAPilotCQProject

Rational TestManager

TestManager Artef acts

Sybase SQL Anywhere

Network Database Serv er -ASA8Service01Local sy stem accountServ ice Group -ASANYServer Rational Rose Model

Page 11© 2005 Electronic Data Systems Corporation. All rights reserved.© 2005 Electronic Data Systems Corporation. All rights reserved.

Test Fast – IBM-Rational ToolsTest Fast – IBM-Rational Tools

Implemented Test Scripts

Project Requirements

Vision

Use CaseSpecif ications

SupplementaryRequirements

TA Risks

Rational RequisitePro

Use Case (UC)

Rational XDE Modeler

Use Case ModelElement 3

Use Case (UC) requirements in RequisiteProare linked to Use Case Model Elements in

XDE Use Case Models

Initial documents are basedon RUP MS Word templates

Rational ClearQuest

Project Risks

Def ects

Change Requests

Glossary

Stakeholder Request (STRQ)

Feature (FEAT)

Supplementary Req (SUPL)

TA Risk (RISK)

Rational TestManager

Test Plans

Test Cases

Test Suites and Builds

Def ects discov eredwhile executing tests arerecorded in ClearQuest

Functional Use Case (UC) and non-f unctional Supplementary (SUPL)requirements in RequisitePro areinputs to Test Cases in TestManager

1

1

Use Case ModelElement 2

Use Case ModelElement 1

2

Design Elements in XDE Use CaseModels are inputs to Test Cases inTestManager

2

Functional TesterTest Scripts f or Web / VB /

Jav a Apps

TA Pilot.rqs

<XDE ModelerDatabase>

<ClearQuest UserDatabase>

<TestManager DataStore>

Test Iterations

Test Execution Logs

Robot Test Scriptsf or .NET, C++ and other

Apps

PurifyPlus Test Scriptsf or Dev eloper testing

Performance TesterTest Scripts (Load Testing)

SiteCheck Test Scriptsf or Web Site testing

ManualTest Test Scriptsf or manual testing

Rational XDE Modeler isprov ided as part of Rational

XDE Dev eloper Plus f or Jav a

Page 12© 2005 Electronic Data Systems Corporation. All rights reserved.© 2005 Electronic Data Systems Corporation. All rights reserved.

Questions?Questions?Questions?Questions?

04/10/23 14:37

EDS and the EDS logo are registered trademarks of Electronic Data Systems Corporation. EDS and the EDS logo are registered trademarks of Electronic Data Systems Corporation. EDS is an equal opportunity employer and values the diversity ofEDS is an equal opportunity employer and values the diversity ofits people. © 2005 Electronic Data Systems Corporation. All rights reserved. its people. © 2005 Electronic Data Systems Corporation. All rights reserved.

eds.comeds.comSharon PickenSharon PickenEDS Global Testing ForumEDS Global Testing Forum