2 selenium-aakar gupte

22
Selenium Framework Presented By: Aakar

Transcript of 2 selenium-aakar gupte

Page 1: 2 selenium-aakar gupte

Selenium Framework

Presented By:Aakar

Page 2: 2 selenium-aakar gupte

AgendaWhat is Automation Testing?Myth vs. Reality of Automation TestingIs complete Test Automation always good?What do we Automate?Why do we AutomateTypes of Automation ToolsWhat is FrameworkHow to choose FrameworkFramework KitTypes of Automations Testing FrameworksKey Features of Framework

Page 3: 2 selenium-aakar gupte

What is Automation Testing?

Page 4: 2 selenium-aakar gupte

Myth vs. Reality of Automation Testing

MythsAutomated testing always results

in improved software quality

Every application development project or testing team can use

automated testing tools

Automated testing is an all or nothing

RealitiesAutomated testing requires a

higher initial investment but can yield a higher ROI

Skills and training are required to be successful with any automated

testing tool Every company doing automated testing still does some amount of

manual testing

Page 5: 2 selenium-aakar gupte

Is complete Test Automation always good?

Page 6: 2 selenium-aakar gupte

What do we Automate?Repetitive tests that run for multiple builds

Frequently-used functionality that introduces high risk conditions

Tests that run on several different hardware or software platforms and configurations

Tests that take a lot of effort and time when doing manual testing

Page 7: 2 selenium-aakar gupte

Why do we AutomateItems Cost Time

Builds and Executing Testing Manual Days

Develop Manual Tests 2 tester @ 50$/-day 4 days(400)

Execute Manual tests 2 testers @ 50$/-day 1 day(100)

Maintain Manual tests 1 tester @ 50$/- day Alternate day(50)

Total 550

Automation

Execute automated tests 1 tester @ 50$/- day 2-3 hours (6.25$/- hr)

Maintain automated test 1 tester @ 50$/- day 1 day(50)

Develop automated tests 1 tester @ 50$/-day 5 days(250)

Total 310

Cost of 1st Build Cycle

Cost of 1st Build Cycle

Page 8: 2 selenium-aakar gupte

Types of Automation ToolsLimited to Firefox

No Database testing

No Error handling

Page 9: 2 selenium-aakar gupte

What is Framework?Set of common software building blocks

No need to start from scratch every time

Reusability

Page 10: 2 selenium-aakar gupte

How to choose Framework?

Page 11: 2 selenium-aakar gupte

Framework Kit

Selenium Framework

Data Sources

Continuous Integration

Technologies

Logging

Reporting

Development

ExcelDatabaseMS Access

HtmlGraphsTestNG

3rd partyLog4j

EclipseNet BeansVisual Studio

JavaPythonPerlC#Ruby

JenkinsAntScheduling

Page 12: 2 selenium-aakar gupte

Types of Automations Testing Frameworks Independent

scripts

Using data sources like excel

Reusability of functions

Maintenance, all frameworks covered

Page 13: 2 selenium-aakar gupte

Key Features of FrameworkAutomation on diverse set of applications

HTML reports and emailing

Flexible and extensible

Consolidated summary reports

Selective test scripts

Page 14: 2 selenium-aakar gupte

Project StructureProject Name

SRC

Packages

drivers

jars

Page 15: 2 selenium-aakar gupte

Project Structure

Main Method

Read Data

Read Prop. File

Xlsx Report

Page 16: 2 selenium-aakar gupte

Project StructureGeneric

Application specific

Only Methods

Page 17: 2 selenium-aakar gupte

Project Structure

Only Logs

Page 18: 2 selenium-aakar gupte

Project Structure

Only Logs

Page 19: 2 selenium-aakar gupte

Project Structure

Constants

Page 20: 2 selenium-aakar gupte

Demo

Page 21: 2 selenium-aakar gupte

Q & A

Page 22: 2 selenium-aakar gupte

Thank You