Comparison Of Automation And Manual Testing - Pixel Values Technolabs

1. Comparison Of Automation And Manual Testing Presented By Pixel Values Technolabs

2. OBJECTIVES What is Automation Testing? 01 Challenges and How to overcome them 02 Technologies 03 Benefits of Automation Testing 04 Possible Solutions 05 Short / Mid / Long term plan. Risks & Mitigations 06 Implementation 07

3. WHAT IS AUTOMATION TESTING? • “The management and implementation of test activities whichinclude the development and execution of test scripts so as to verify test requirements, using an automated test tool.”

4. CURRENT CHALLENGES SAME EFFORT EACH TIME CONTINOUS DELIVERY SCOPE LESS REGRESSION TIME MONOTONOUS WORK HIGH CHANCES OF MISSING SOMETHING COST OF FAILURE COST

5. WAYS TO OVERCOME CHALLENGES • Deploying more testers • Increasing the schedules • Scope reduction • AUTOMATION

6. TECHNOLOGIES

7. CONFIDENCE EARLYBUGS MORALE REUSABLE SCOPE CUSTOMER RETENTION TIMETOMARKET QUALITY COST BENEFITS OF AUTOMATION TESTING TIME BENEFITS

8. AUTOMATION v/s MANUAL TESTING (SAVING TIME & COST) • Effort and Cost • Lets assume 10 test cases • Effort required to write 10 test cases manually => 6hrs. • Effort required to run all 10 cases manually => 2hrs. • Effort required to write auto tests for all 10 cases => 12hrs. • Effort required to run auto tests for all 10 cases => < 1 min • Number of testing iterations => 5 • Total manual testing time => 16hrs. • Total auto testing time => 12hrs.

9. POSSIBLE SOLUTIONS Possible solutions are: Buy a third party test framework. Build a test automation team (separate from existing manual testing team). Create an hybrid test automation team with existing manual testers to develop an in-house test framework.

10. CRITERIA FOR SOLUTION SELECTION • Solution Criteria • A successful solution meets the following criteria: • Minimal impact to the existing budget (manual testers salaries are already included in the budget) • Involves minimal purchases • Minimal impact to the current schedule, and there are no changes anticipated to the future schedules • Benefits accumulate because the test suite grows over time • Addresses the situation over the longer term

11. SHORT/MID/LONG TERM PLAN LONGTERM SHORTTERM MIDTERM Test suite selection and prioritisation Stabilizing the framework • Starting small with pilot project Maintenance & enhancement When to automate Simpler framework for ease of use Evolving process Expectation setting. MVP (Minimum Viable Product) Training existing manual testing team Framework integration Automate other products / processes in the company Team ramp up White label Open source software tools Advanced Trainings Keeping shorter delivery milestones

12. RISKS & MITIGATIONS Can’t tell if something ‘looks Good’, or pictogram or window not displayed well Sanity by manual testers Backup Server Server Downtime Attrition of manual Testers Training the manual testers Changes made in the interface Share the changes with QA team

13. ROADMAP AHEAD PROTOTYPE FEASIBILITY TEAM TOOLS IMPLEMENTATION To organize a meeting with the key software developers and product testers to begin analysing the requirements and planning the design of the new framework • A good mix of domain experts and automation experts • What to automate? • What not to automate? • When to automate? • Coverage? • Time? • Cost? • Framework to be used. • Tools to be used for integration, repository, scripting etc. (Freeware / licensed) • Milestone basis • Powerful reports & Metrics • Seamless integration • Scalable and Customizable • A working prototype which can be showcased to the stakeholders and as a base for defining long term roadmap(out of merits / demerits from different solutions available). • Process set-up • Financial benefits • Hardware/Software requirement

14. Contact Us