Insoft training day_1
Download as PPTX, PDF0 likes76 views
This document provides an agenda for a presentation on automated testing. It begins with introductions and background information. It then outlines the roadmap and prerequisites for manual testing. The document discusses Java programming basics and moves to discussing what automated testing is, when it can be started, what can be automated, and potential issues. It concludes by highlighting the benefits of automated testing such as reduced time and costs, increased coverage, and supporting agile releases.
Insoft training day_1
- 2. Agenda Introduction What is your name Back groud Why you came here How do you know about US What you can cook best in this WORLD Do you have iPHONE?
- 3. Next About Me What you will learn here How to convert your manual testing efforts to Automated Testing Understand Role of technical Tester
- 4. Road Map - Prerequisites 1. Manual Testing 1. Test plan 2. Test Case 3. Bug Life cycle 4. Agile 5. Agile Testing 6. SDLC 7. Different types of testing
- 5. JAVA Datatypes Strong in coding Exceptions OOPS Class method and object ….
- 6. Agenda Automated testing ??? what is all about So when can I start this cool stuff?? So what is that I can automate What can go wrong as always??? What are the real Benefits at nut shell
- 7. Lets Start Automation Testing is cool…..... Any Question ?.... NO/YES
- 8. Whats Automation Testing Do you know what is manual testing at first place Do you know what is Agile Testing Do you know what is BDD
- 9. Why to automate Reparative testing Release X Spring X Env X Retesting X Device Data driven testing Multi Device testing * Regression testing
- 10. For Manual Testers Release based only and not used much
- 11. Automation testing Its about automating your manual testing efforts Should have a manual test cases for us to convert into them And run them when ever you want.. but don’t forgot if your manual test cases is good your automated test cases will be good Run them over night on any environment, browser etc. Its not compliment of manual testing but a supplement
- 12. When to start automate testing If we know what we want to test repetitively Have regression pack ready Know the target browsers and environments
- 13. What can be automated All user journeys - to make sure what ever happened to the code user will not be effected All 3rd party integrations tests – to make sure all 3rd party systems are always running fine Tests which have probability to add more test combinations – Single tests can be used to run more test combinations to increase more coverage and all edge cases All regression and repetitive tests – every test which need to be run atleast 2 times in future
- 14. What can go wrong If scope is not properly defined Code too complex to maintain – Don’t develop new application which have bugs in self – make it simple and easily maintained UI is not stable Don’t have proper test data – tests fails because the data is not found in the test environment or data is refreshed Too many changes in Code Synchronization issues
- 15. Benefits Reduce Time – Running tests over night on remote machine Reduce cost of unseen bugs in release candidate Test Coverage with Data driven tests Cross browser – More environments Faster feed back Reduce manual testing Supports Agile release cycle testing Faster release with quality product BDD in future