This talk was given during the Asia Agile Test Alliance Conference 2015. ThiIn this presentation the Agile test practices were mapped to the continuous delivery practices. The presentation provides quick view about the broad anti patterns and then provide the key solution by following the Onion Layered Test Practice Map (Task, Story, Sprint, Release Level). It is well known that without good test practice and quality test, continuous delivery may only give false confidence.
20. Layered Automation Framework –A simple Case
Start
Step a
Step b
Step c
Step d
Step e
Step f
Step g
Step h
Step i
Step j
End
Test Cases Before Layering
Change in any small functionality can
impact steps and as an impact all Test
Cases have to be re-worked to adapt to
new change – Result : Huge Rework
effort and poor maintainability
Impact Of functional change on Test cases
before Layering
Start
Step a
Step b
Step x
Step d
Step y
Step z
Step g
Step h
Step i
Step j
End
Start
Step a
Step b
Step c
Step d
Step p
Step q
Step r
Step g
Step h
Step i
Step j
End
Step a
Step b
Step x
/Step c
Step d
Function 1
(input = Type x/c)
Step g
Step h
Step I
Step j
Function 2()
Start
Function1(c)
Step e
Step f
Function2()
End
Test Cases after Functional Layering
Most Change in functionality can be
reworked at functional or business layer
level – Result : Very Less Rework effort,
High maintainability and Reusability
Impact Of functional change on Test cases
after Layering
Start
Function1(x)
Step y
Step z
Function2()
End
Start
Function1(c)
Step p
Step q
Step r
Function2()
End
Start
Buss Func 1(e,f)
End
Start
Buss Func 1(y,z)
End
Start
Buss Func 1(p,q,r)
End
Test Cases after Business Layering
Buss Func 1(input = Steps)
• Function 1
(input = Type x/c)
• Steps based on input
• Function 2()