How selenium can transform your qa career

How selenium can transform your qa career

• 1.
  HOW SELENIUM CANTRANSFORM YOUR QA CAREER Shama Ugale
• 2.
  AGENDA  What isTest Automation Testing ??  Why and when to Automate ??  Automation Myths and Reality  Automation Vs Manual  Tools in the Market  Selenium – The myth and Truth  Who are you ??  How can Selenium help you ??  Do you can you really learn Selenium ??  Then How and What ??
• 3.
  WHAT IS TESTAUTOMATION ??  Test automation is the use of software :  - To set test preconditions.  - To control the execution of tests.  - To compare the actual outcomes to predicted outcomes.  - To report the Execution Status.  Commonly, test automation involves automating a manual process already in place that uses a formalized testing process.
• 4.
  WHY AND WHENTO AUTOMATE?  Frequent regression testing  Repeated test case Execution is required  User Acceptance Tests  Faster Feedback to the developers  Reduce the Human Effort  Test same application on multiple environments
• 5.
  MYTH - TESTAUTOMATION IS SIMPLE, THAT EVERY TESTER CAN DO IT  This myth is promoted by the tool sales people. They are trying to promote the following test automation process:  - Record the script  - Enhance the script by adding functions and data driving  - Run the scripts  - Report results  Under the influence of this myth the QA manager can proudly report: All our testers are developing test automation.
• 6.
  REALITY - TESTAUTOMATION IS A SOFTWARE DEVELOPMENT TASK  Automation should be designed, developed and tested  You need to have some kind of a programming background to implement test automation. Test Automation is not as complex as C++/C#/Java development.  Test automation standards should be developed  Automated test components are assets that should be treated like application source code
• 7.
  AUTOMATED TESTS VSMANUAL TESTS  Manual Testing is boring  - No one wants to keep filling the same forms  - There is nothing new to learn when one tests manually  - People tend to neglect running manual tests  - No one maintains a list of the tests required to be run if they are  manual tests  Automated Tests on the other hand are code  - They are fun and challenging to write  - One has to carefully think of design for reusability and coverage  - They require analytical and reasoning skills  - They represent contribution that is usable in the future
• 8.
  AUTOMATED TESTS VSMANUAL TESTS  Manual Testing is not reusable  - The effort required is the same each time  - One cannot reuse a Manual Test  Automated Tests are completely reusable - IMPORTANT: One needs to setup a Continuous Integration - Server, a common Code Repository and a organization structure  - Once written the Automated Tests form a part of the codebase - They can be reused without any additional effort for the lifetime - of the Project
• 9.
  AUTOMATED TESTS VSMANUAL TESTS  Manual Tests provide limited Visibility and have to be Repeated by all Stakeholders  Only the developer testing the code can see the results  Tests have to be repeated by each stakeholder  For eg Developer, Tech Lead, GM, Management  Automated Tests provide global visibility  Developers, Tech Leads and Management can login and see Test Results  No additional effort required by any of them to see the software works!!
• 10.
  AUTOMATED TESTS VSMANUAL TESTS  Manual Testing requires complex Manual Setup and Tear Down  - Can involve frequently running db queries  - Can involve making changes to backend servers  - Steps become more complex with multiple dependent test cases  Automated Tests can have varying scopes and require less complex setup and teardown  - Unit Tests have external dependencies mocked – so no setup / teardown required  - Setup and Tear down are automated in Functional Tests using framework support
• 11.
  AUTOMATED TESTS VSMANUAL TESTS  Manual Testing has a high risk of missing out on something  - Each time a developer runs manual tests it is likely he will miss out on an important test case - New developers may have no clue about the battery of tests to be run  Automated Tests have zero risk of missing out a pre-decided test  - Once a Test becomes a part of Continuous Integration – it will run without someone having to remember to run it
• 12.
  AUTOMATED TESTS VSMANUAL TESTS  Effort and Cost  Lets assume 6 test cases  Effort required to run all 6 manually => 10 min  Effort required to write unit tests for all 6 cases => 10 min  Effort required to run unit tests for all 6 cases => < 1 min  Number of testing iterations => 5  Total manual testing time => 50 min  Total unit testing time => 10 min Release Manual Test Auto Test Manual Test Cumulative 1 10 10 10 2 10 0 20 3 10 0 30 4 10 0 40 5 10 0 50 Release Manual Test Auto Test Manual Test Cumulative 1 10 10 10 2 10 0 20 3 10 0 30 4 10 0 40 5 10 0 50
• 13.
  MAIN REASONS FORTEST AUTOMATION FAILURES  Lack of Management Support  Inexperienced Test Automation staff  Over-engineering
• 14.
  Myth :  Opensource so no cost  Widely used  Very complex  Your future work Truth : • No license, but more expensive skill • More popular than implemented • Not that tough , when learnt in right way 14 SELENIUM - THE MYTH AND TRUTH
• 15.
   New toIT  QA  Non-QA IT guys  QA Lead / Manager  IT Leader 15 WHO ARE YOU ??
• 16.
   Getting yourfirst QA job.  For your upcoming automation project  Get a promotion at work  Saving project cost  Not sure …. confused 16 HOW CAN SELENIUM HELP YOU ??
• 17.
   Getting Hired Getting projects  It gives hope  Multi-skilled 17 HOW CAN SELENIUM TRANSFORM YOUR CAREER ??
• 18.
   I haveno clue, don’t know where and how to start .  I have never written code  Java scares me.  Am I even Capable.  Little bit all of the above 18 WHAT IS YOUR BIGGEST FEAR IN LEARNING SELENIUM ??
• 19.
   Fundamentals ofAutomation  Selenium Introduction  Core Java  Junit , TestNG  Element Identification.  Webdriver (Selenium 2.0)  Automation Frameworks 19 WHAT TO LEARN ??
• 20.
   Trained hundredsof professionals  Practical projects  Well organized and rich course content  Strong emphasis and hands on coding.  Forum for further assistance 20 AM I SURE?? YES… HOW ??
• 21.
  THANK YOU