How selenium can transform your qa career
Download as pptx, pdf0 likes236 views
This document discusses how learning the test automation tool Selenium can transform a QA professional's career. It begins by defining test automation and discussing why and when tests should be automated. It addresses common myths around test automation, comparing automated and manual testing. The document then discusses Selenium specifically, clarifying myths and truths about it. It considers different types of learners who might learn Selenium and how it could help with jobs, promotions, and project costs. Finally, it addresses common fears around learning to code with Selenium and provides recommendations on what to learn.
More Related Content
What's hot (20)
Similar to How selenium can transform your qa career (20)
Recently uploaded (20)
How selenium can transform your qa career
- 1. HOW SELENIUM CAN TRANSFORM YOUR QA CAREER Shama Ugale
- 2. AGENDA ļ¢ What is Test 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 TEST AUTOMATION ?? ļ¢ 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 WHEN TO 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 - TEST AUTOMATION 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 - TEST AUTOMATION 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 VS MANUAL 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 VS MANUAL 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 VS MANUAL 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 VS MANUAL 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 VS MANUAL 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 VS MANUAL 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 FOR TEST AUTOMATION FAILURES ļ¢ Lack of Management Support ļ¢ Inexperienced Test Automation staff ļ¢ Over-engineering
- 14. Myth : ļ¢ Open source 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 to IT ļ¢ QA ļ¢ Non-QA IT guys ļ¢ QA Lead / Manager ļ¢ IT Leader 15 WHO ARE YOU ??
- 16. ļ¢ Getting your first 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 have no 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 of Automation ļ¢ Selenium Introduction ļ¢ Core Java ļ¢ Junit , TestNG ļ¢ Element Identification. ļ¢ Webdriver (Selenium 2.0) ļ¢ Automation Frameworks 19 WHAT TO LEARN ??
- 20. ļ¢ Trained hundreds of 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