Embed Size (px)
Citation preview
AgendaIntroduction
What is your nameBack groudWhy you came hereHow do you know about USWhat you can cook best in this WORLDDo you have iPHONE?
NextAbout MeWhat you will learn hereHow to convert your manual testing efforts to Automated TestingUnderstand Role of technical Tester
Road Map - Prerequisites1. Manual Testing
1. Test plan2. Test Case3. Bug Life cycle4. Agile5. Agile Testing6. SDLC7. Different types of testing
JAVADatatypesStrong in codingExceptionsOOPSClass method and object ….
Agenda
Automated testing ??? what is all aboutSo when can I start this cool stuff??So what is that I can automateWhat can go wrong as always???
What are the real Benefits at nut shell
Lets StartAutomation Testing is cool….....
Any Question ?....NO/YES
Whats Automation Testing
Do you know what is manual testing at first placeDo you know what is Agile TestingDo you know what is BDD
Why to automateReparative testing
Release X Spring X Env X Retesting X DeviceData driven testingMulti Device testing *Regression testing
For Manual TestersRelease based only and not used much
Automation testingIts about automating your manual testing efforts Should have a manual test cases for us to convert into themAnd run them when ever you want.. but don’t forgot if your manual test cases is good your automated test cases will be goodRun them over night on any environment, browser etc.
Its not compliment of manual testing but a supplement
When to start automate testingIf we know what we want to test repetitivelyHave regression pack ready
Know the target browsers and environments
What can be automated All user journeys - to make sure what ever happened to the code user will not be effectedAll 3rd party integrations tests – to make sure all 3rd party systems are always running fineTests 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
What can go wrongIf scope is not properly definedCode too complex to maintain – Don’t develop new application which have bugs in self – make it simple and easily maintainedUI is not stableDon’t have proper test data – tests fails because the data is not found in the test environment or data is refreshedToo many changes in Code
Synchronization issues
BenefitsReduce Time – Running tests over night on remote machineReduce cost of unseen bugs in release candidateTest Coverage with Data driven testsCross browser – More environments Faster feed backReduce manual testingSupports Agile release cycle testingFaster release with quality product
BDD in future
