1. Test Automation Support Systems
Layered Architecture
Rahul Verma
Consulting Software Tester and Coach
QA Architect, McAfee India (An Intel Company)
www.testingperspective.com
2. Agenda
• Test automation frameworks
• Test Automation Support System
• Design elements
• Framework as a Layer
• The possibilities
… not necessarily in that order
ReusableGenericModularExtensible-----Home-grown frameworks don’t build:impose a common end to end processDefined test structuresTesters start picking up modules out of contextModularExtensibleReusableGenericSemi-Strict: Imposes a minimalistic processHelps in defining the automation test strategyCan support any sort of design of frameworks: data driven/keyword drive/mutation/generation/ATDD
ReusableGenericModularExtensible-----Home-grown frameworks don’t build:impose a common end to end processDefined test structuresTesters start picking up modules out of contextModularExtensibleReusableGenericSemi-Strict: Imposes a minimalistic processHelps in defining the automation test strategyCan support any sort of design of frameworks: data driven/keyword drive/mutation/generation/ATDD
ReusableGenericModularExtensible-----Home-grown frameworks don’t build:impose a common end to end processDefined test structuresTesters start picking up modules out of contextModularExtensibleReusableGenericSemi-Strict: Imposes a minimalistic processHelps in defining the automation test strategyCan support any sort of design of frameworks: data driven/keyword drive/mutation/generation/ATDD
ReusableGenericModularExtensible-----Home-grown frameworks don’t build:impose a common end to end processDefined test structuresTesters start picking up modules out of contextModularExtensibleReusableGenericSemi-Strict: Imposes a minimalistic processHelps in defining the automation test strategyCan support any sort of design of frameworks: data driven/keyword drive/mutation/generation/ATDD