The document discusses best practices for automation testing, emphasizing criteria for selecting tools, determining timing, and identifying suitable testing environments. It highlights that not all test scenarios should be automated and suggests creating a smoke test for basic application behaviors. Additionally, it recommends involving manual testers and ensuring scripts are independent and well-structured.

1. HHWWWin
Automation
TestingMarch21,2018

2. AboutMe
JuliusGlifonea,AutomationLead
ExistSoftwareLabsInc
SeleniumWebDriverJava/Ruby

3. Howtoselect
automation
testingtool?
1.Cultureofthecompany
2.TrialVersionofthetool(Paid)
3.CostoftheTool/ProjectBudget
4.Resource(s)knowledge

4. Whentostart
automationin
theproject?
Notallprojectneedstobeautomated.
1.Considerthelengthoftheprojectfirst.
2.Timingofautomationtesting(eg:After3
sprints/Afterthefirstreleaseetc.)

5. Whereto
automate?
1.Controlledtestenvironment.
2.Preferably,aseparatestagingenvironment
dedicatedonlyforautomation.
a.Toreducefrequentdebugging,down-times
anddataconflictwithothertestersand
developers
b.Avoidsuddenfailureduetonewfeatures
implementedonthelatestiteration

6. Whatto
automate?
1.Automatetestcasescreatedbymanual
testers.
2.Notallscenariosneedstobeautomated
3.Notallscenarioscanbeautomated
Additional:
1.Createasmoketestingorhappypathfor
thebasicbehavioroftheapplication.
2.Discusswiththemanualtesters,whatwill
benefitthemthemost
3.Monitorscriptingcoverage
4.Addcomplicatedscenarioslater(PMT)

7. Howtodoit?
1.DevelopFramework(Module/Data-Driven/
Hybrid/Keywordetc)
2.ConsidertalkingwiththeUI/UXdev(WEB)
3.Scriptsshouldbeautonomous
4.Pageobjectmodel
5.Manymoretoconsider