Day 2

Why Automation Projects fail? --- PAIN AT CLIENTS END

Not right people

Not right framework

Not enough budget/resources

Not enough planning

No motivation … Apps must be tested, when it comes to release we will focus on quick manual smoke test to clear the gate from Dev --- Staging ---- Testing ---- Production

Application is always changing(?). Not necessarily. Content, upgrades/modifications and UI.

Over complicating it.

Setting right expectations on % of automation.

Too much coding, so no QA can look at.

Shift Right also happened.

Wrong Automation Frameworks

Trying too much of BDD, ATDD, script-free scripts.

Manual Test Engineers should have atleast been able to run and maintain Automation Frameworks.

What are clients looking for in QA/Automation professionals? --- solution in your hand.

AUT - SAMPLE app that we can all work

Able to login and test.

Simple to understand

Create few test cases

Automate using Selenium

Training Project 1 (5-6 session) - Linear and Functional Decomposition Framework

Selenium IDE

Element Identification - xPath

Selenium WebDriver, Eclipse, Java, JUnit/TestNG

Hands-On practice