Bug deBug Chennai 2012 Talk - Test automation support systems layered architecture by Rahul Verma
•Télécharger en tant que PPTX, PDF•
0 j'aime•525 vues
Recommandé
Recommandé
Contenu connexe
En vedette
En vedette (12)
Similaire à Bug deBug Chennai 2012 Talk - Test automation support systems layered architecture by Rahul Verma
Similaire à Bug deBug Chennai 2012 Talk - Test automation support systems layered architecture by Rahul Verma (20)
Plus de RIA RUI Society
Plus de RIA RUI Society (20)
Dernier
Dernier (20)
Bug deBug Chennai 2012 Talk - Test automation support systems layered architecture by Rahul Verma
- 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
- 3. Open Discussion Test Automation Frameworks
- 4. Test Automation Support System
- 5. Framework Features • Extensible • Reusable • Modular • Learnable • User-friendly • Portable • Scalable • Abstractions • … More?
- 6. Automation Support features • Distributed Testing • Script Development Environment • Support multiple interfaces – web , gui, cli • Support multiple SUTs • Run-time infrastructure behavior modification • Multiple modes of execution • Cross-platform • Multi-deployment support • … More?
- 8. Relations Configuration Code S1 S2 S3 S4 S5 S6 S7
- 9. Steps Could be… • Build Registration • Test Cycle Configuration • Schedule Configuration • Schedule allocation • Schedule Pickup • Schedule Execution • Reporting
- 10. Hooks • Pre-processors • Processors • Post-processors
- 11. Schedule Schedule Build Test Cycle Scheduling Schedule Allocation Pick-up ( Test Reporting Registration Configuration Tests Execution (Controller) Runner) Schedule Schedule Build Test Cycle Scheduling Schedule Allocation Pick-up ( Test Reporting Registration Configuration Tests Execution (Controller) Runner)
- 12. Schedule Schedule Build Test Cycle Scheduling Schedule Allocation Pick-up ( Test Reporting Registration Configuration Tests Execution (Controller) Runner) Schedule Schedule Build Test Cycle Scheduling Schedule Allocation Pick-up ( Test Reporting Registration Configuration Tests Execution (Controller) Runner)
- 15. Thanks Rahul_Verma@testingperspective.com www.testingperspective.com
Notes de l'éditeur
- 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