Upload
ocean-dong
View
541
Download
4
Tags:
Embed Size (px)
DESCRIPTION
A software dev team implemented agile testing way. This presentation is a nice summary.
Citation preview
Infor Confidential Copyright © 2001-2008 Infor Global Solutions
Agile Testing Experiment in BIS
2
Quick Background Info
About BIS
About Automated Testing of BIS
Let’s Start With What’s Agile?
3 Copyright © 2001-2006 Infor Global Solutions
Agile Means…
Kill Waste
4 Copyright © 2001-2006 Infor Global Solutions
What’re Wastes?
Too MuchToo Early
Too Little
Too Late
Duplicate
5 Copyright © 2001-2006 Infor Global Solutions
Previously…
Duplicate
Too Late/Little
6 Copyright © 2001-2006 Infor Global Solutions
Can You Imagine…
Iteration N
RELEASE By Every Iteration
7
How BIS Does
IMMEDIATE Scripting
+
Keep Scripts ALIVE
8
IMMEDIATE Scripting
Benefit:RICHER “Done”: Both Production Code And Testing Suite
9
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: EASY Scripting
10
IMMEDIATE Scripting: EASY Scripting (1)
Easy DSL Wrapper
Scripting LIKE Writing Test Case
Low Level Scripting
(BIS Testing) Domain Specific Language
11
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
12 Copyright © 2001-2006 Infor Global Solutions
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
13 Copyright © 2001-2006 Infor Global Solutions
Behind IMMEDIATE Scripting: BIS AT Framework
14 Copyright © 2001-2006 Infor Global Solutions
Take a Break. 10 Slides Left.
Coming Next: Keep Scripts ALIVE
15
Keep Scripts ALIVE
Benefit:More RELIABLE “Done”: Not Only Verify New Features, But Also Ensure Old Ones Unbroken
REGRESSION Everyday
16
Keep Scripts ALIVE
Challenges
• Complexity In Running Bulk Scripts
• Large Effort of Result Analysis
• Adapt To Current Development Process
Solution:
CQC (Continuous Quality Checking)
17
Keep Scripts ALIVE: CQC Server
The (N+1)th Tester
BIS
Fully Automatic
Customized Process
Smart Reporting
18 Copyright © 2001-2006 Infor Global Solutions
Keep Scripts ALIVE: CQC Process
19
Keep Scripts ALIVE: CQC Driven Development
20
That’s All?
People s Improvement
IMMEDIATE Scripting
+
Keep Scripts ALIVE
+
?
21
People’s Improvement
When’s the Best Time To Start Automating?
Can We Really Trust Automated Test?
Is Finishing Script On Time As Important As Finishing Feature Construction?
Mind Change
Better Planning
New Feature First And Bug Fixing Second?
Is Testing Just Tester’s Work?
22
In the Future, or Soon…
Better DSL With Groovy
Distributed CQC
Easier Bug Reporting/Reproducing With CQC
Scripting For Bug
23
Thanks