TEST AUTOMATION
Presentation T14 :
Success with
Automated
Regression Test
EuroSTAR December 2009
Ane Clausen ©
2
Speaker
Master of Science in Computer Science,
Copenhagen University
Have been working with IT for the last 23 years:
8 years with test as a test manager
2 years with automated test
3
Agenda
Background
Strategy
Practice
Production
Benefits of Automated Test
Success Criteria
Questions
4
Background
Problem: Increasing complexity of IT-insurance system
Solution: Automated Regression Test
• Organization
-task embedded in management, business, IT
-management support
• Work process
-all recognize the tasks and responsibilities
• (Infra-)Structure
-location
• System Environment Citrix
-Quality Center with Business Process Testing
-Quick Test Professional
5
Strategy
Goal: go – no go
Project
• Pilot-project 3 months
• Only automated test
• Start with positive test
• Clear goals
• ”Keep it simple”
Work Processes
• Few persons
-100% dedicated
• Agile testing
-iterative, test delivered weekly
• Learning process
-Common reference framework
-Ensure shared knowledge
-Documentation
(standard, best practice, log)
• Help from (tool-)expert
6
Practice
Where to begin automated test:
• Select a real business (insurance) application
• Stable application
• Simple function
• Limited scope
• Automate a small area ”end to end” (logon-logoff)
• Easy to continue working with
7
Practice -Example Insurance Appl.
General
reused:
custom,
business
Specific
used once:
coverage
8
Practice – Example Overview
Application structure
Capital
Pension Rate Policy
:
Private Dog
Car Policy
:
logon Business Building Policy logoff
Agricultural
Technical
:
Test case structure
Automated test
Pension
Private
Business
General Business
tc1:business type
tc2:custom details
Building
tc3: protected house
Agricultural
tc4: farm cows coverage
tc5: farm pigs coverage
General test cases
tc6: Logon
tc7: Policy
tc8: Logoff
9
Practice
Build the test so it reflects the real application
Size:
• Well-arranged test case
- composite test cases: general/specific
Structure:
• Structure the test cases in a business oriented way
- easy to locate test cases and maintain an overview
Name:
• Naming convention
- recognize and understand test cases
10
Test report
11
Production
Agreements on procedures before production
• Developer describes functionality and changes in GUI
in the Change Management System
• Delivery Manager agrees on time schedule
• Automated regression test takes 3 days to execute
including bugfixing and retesting
• Visible Quality. Every automated test ends up with a
test report describing test coverage
• Business wants more test cases – you need a process
for the work to continue
12
Benefits of Automated Test
• The Automated test was in Production with limited
scope after 3 months and all of it after 6 months
• Small success motivates
• Automated test helps ensure quality
• Automated test finds serious errors
• Can execute test in many environments (citrix)
• Can execute the test when we want
• Same regression test every time
• Big acknowledgement both in-house and outside
13
Success Criteria
1. Task and responsibility must be agreed on and
known in the organization
2. Make a pilot project and define clear goals
3. Ensure common understanding, knowledge and
document best practice and standards
4. Understanding the whole business application
ensures the right structure and size of test cases
5. ”Keep it simple”
14
QUESTIONS
abancs@almbrand.dk

Ane Clausen - Success with Automated Regression Test revised

  • 1.
    TEST AUTOMATION Presentation T14: Success with Automated Regression Test EuroSTAR December 2009 Ane Clausen ©
  • 2.
    2 Speaker Master of Sciencein Computer Science, Copenhagen University Have been working with IT for the last 23 years: 8 years with test as a test manager 2 years with automated test
  • 3.
  • 4.
    4 Background Problem: Increasing complexityof IT-insurance system Solution: Automated Regression Test • Organization -task embedded in management, business, IT -management support • Work process -all recognize the tasks and responsibilities • (Infra-)Structure -location • System Environment Citrix -Quality Center with Business Process Testing -Quick Test Professional
  • 5.
    5 Strategy Goal: go –no go Project • Pilot-project 3 months • Only automated test • Start with positive test • Clear goals • ”Keep it simple” Work Processes • Few persons -100% dedicated • Agile testing -iterative, test delivered weekly • Learning process -Common reference framework -Ensure shared knowledge -Documentation (standard, best practice, log) • Help from (tool-)expert
  • 6.
    6 Practice Where to beginautomated test: • Select a real business (insurance) application • Stable application • Simple function • Limited scope • Automate a small area ”end to end” (logon-logoff) • Easy to continue working with
  • 7.
    7 Practice -Example InsuranceAppl. General reused: custom, business Specific used once: coverage
  • 8.
    8 Practice – ExampleOverview Application structure Capital Pension Rate Policy : Private Dog Car Policy : logon Business Building Policy logoff Agricultural Technical : Test case structure Automated test Pension Private Business General Business tc1:business type tc2:custom details Building tc3: protected house Agricultural tc4: farm cows coverage tc5: farm pigs coverage General test cases tc6: Logon tc7: Policy tc8: Logoff
  • 9.
    9 Practice Build the testso it reflects the real application Size: • Well-arranged test case - composite test cases: general/specific Structure: • Structure the test cases in a business oriented way - easy to locate test cases and maintain an overview Name: • Naming convention - recognize and understand test cases
  • 10.
  • 11.
    11 Production Agreements on proceduresbefore production • Developer describes functionality and changes in GUI in the Change Management System • Delivery Manager agrees on time schedule • Automated regression test takes 3 days to execute including bugfixing and retesting • Visible Quality. Every automated test ends up with a test report describing test coverage • Business wants more test cases – you need a process for the work to continue
  • 12.
    12 Benefits of AutomatedTest • The Automated test was in Production with limited scope after 3 months and all of it after 6 months • Small success motivates • Automated test helps ensure quality • Automated test finds serious errors • Can execute test in many environments (citrix) • Can execute the test when we want • Same regression test every time • Big acknowledgement both in-house and outside
  • 13.
    13 Success Criteria 1. Taskand responsibility must be agreed on and known in the organization 2. Make a pilot project and define clear goals 3. Ensure common understanding, knowledge and document best practice and standards 4. Understanding the whole business application ensures the right structure and size of test cases 5. ”Keep it simple”
  • 14.