Agile Testing Experiment In Bis

Agile Testing Experiment in BIS

Infor Confidential

Copyright © 2001-2008 Infor Global Solutions

Quick Background Info 

About BIS



About Automated Testing of BIS

Let’s Start With What’s Agile? 2

Agile Means…

Kill Waste

3

Copyright © 2001-2006 Infor Global Solutions

What’re Wastes?

Too Late

Too Little

Duplicate

Too Early

4

Copyright © 2001-2006 Infor Global Solutions

Too Much

Previously…

Duplicate Too Late/Little

5

Copyright © 2001-2006 Infor Global Solutions

Can You Imagine…

RELEASE

Iteration N

6

Copyright © 2001-2006 Infor Global Solutions

By Every Iteration

How BIS Does

IMMEDIATE Scripting + Keep Scripts ALIVE

7

IMMEDIATE Scripting

Benefit: RICHER “Done”: Both Production Code And Testing Suite 8

IMMEDIATE Scripting

Challenges • Habit’s Change: Script Without Test Case Doc • Much More Time Cost Than Writing Case • Start Scripting Before Feature’s Done • Technical Steps/Verifications

Solution: 9

EASY Scripting

IMMEDIATE Scripting: EASY Scripting (1)

Easy DSL Wrapper (BIS Testing) Domain Specific Language

Scripting LIKE Writing Test Case Low Level Scripting

10

IMMEDIATE Scripting: EASY Scripting (2)

Easy PRECONDITION Facility • Data

Driven Without Script

• Standard Template • Automatic Setup and Teardown • Ensure Independence of Script  No Supposition Before Execution  No Pollution After Execution 11

IMMEDIATE Scripting: EASY Scripting (3)

Easy DEVELOPER’S Support •

Build Agile Testing Infrastructure

•

Implement UI First in Use Case Construction

•

Provide Technical Wrapper Methods

•

Review Script Demo

12

Copyright © 2001-2006 Infor Global Solutions

Behind IMMEDIATE Scripting: BIS AT Framework

13

Copyright © 2001-2006 Infor Global Solutions

Take a Break. 10 Slides Left.

Coming Next:

Keep Scripts ALIVE

14

Copyright © 2001-2006 Infor Global Solutions

Keep Scripts ALIVE

REGRESSION Everyday

Benefit: More RELIABLE “Done”: Not Only Verify New Features, But Also Ensure Old Ones Unbroken 15

Keep Scripts ALIVE

Challenges • Complexity In Running Bulk Scripts • Large Effort of Result Analysis • Adapt To Current Development Process

Solution:

CQC (Continuous Quality Checking) 16

Keep Scripts ALIVE: CQC Server

The (N+1)th Tester Customized Process

BIS Smart Reporting

Fully Automatic 17

Keep Scripts ALIVE: CQC Process

18

Copyright © 2001-2006 Infor Global Solutions

Keep Scripts ALIVE: CQC Driven Development

19

That’s All? IMMEDIATE Scripting + Keep Scripts ALIVE +

People s Improvement ?

20

People’s Improvement

Mind Change  When’s  Can

the Best Time To Start Automating?

We Really Trust Automated Test?

 Is

Finishing Script On Time As Important As Finishing Feature Construction?

 New  Is

Feature First And Bug Fixing Second?

Testing Just Tester’s Work?

Better Planning 21

In the Future, or Soon…

Better DSL With Groovy Distributed CQC Easier Bug Reporting/Reproducing With CQC Scripting For Bug

22

Thanks 23