New Automation Strategy for Verizon Kushan Athukorala

Evolution of Test Automation We are here today Our Goal

Existing Automation Architecture Pros – Easy to design initially Cons – Less Reusability – Less Maintainability – No Separation of Concerns QA Engineer should have java knowledge to understand test code – Less Modular Code Helper Functions Test Code

Layered Automation Architecture Base TestCase Layer Verification Logics Layer - TBD Tasks Layer Business Process Layer - TBD Utility Layer - TBD Test Script Layer Pros – Improved Reusability – Improved Maintainability – Separation of Concerns – Modular Code Cons – Automation Engineer should have good knowledge in java – Needs adherence to Test Automation Design Patterns

Test Automation Design Patterns Test Patterns Catalogue Anti Patterns ?? ObjectClass CreationalTBD Structural1. script-simple pattern 2. script-base pattern 3. script-composed-tasks pattern 4. script-visible-base-composed-tasks pattern 5. script-invisible-base-composed-tasks pattern TBD BehaviouralTBD

Next Steps Reporting Framework Logging Framework Exception Hierarchy Design Automation Wizards Automation Tool Kits Performance Framework Integration

Q&A Do you re-write existing test-suite from the scratch? - No Is seamless migration possible to new strategy? - Yes Where can I get more information / guidelines? Verizon Automation Framework - Optimization Guide.doc - TBD What is the top most prerequisite which drives the new automation strategy? – Well designed TestCases

Thank You