Test Automation Tutorial

Overview of Test Automation

1)    Drawbacks of Manual Testing

•    Manual Testing requires to a greater extent than fourth dimension or to a greater extent than resources
    (Human resources too Environmental Resources), about times both.

•    Performance testing is impractical inwards manual testing
    (Organizing thousands of machines too human users is non possible).

•    Less Accuracy (Human Users may brand mistakes)

•    Executing same tests i time to a greater extent than too i time to a greater extent than is fourth dimension taking procedure every bit good every bit Tedious.

•    Verifying GUI Objects Size differences too Color combinations are non easy
     inwards Manual Testing.

•    Not Suitable for Large scale projects too fourth dimension bounded projects.

•    Batch Testing is non possible, for each too every attempt execution Human
     user interaction is mandatory.

•    Manual Test Case range is really express (Human user tin flaming concentrate on i or
     ii verification points only), if it is Automated test, range is unlimited
    (Tool is software It tin flaming concentrate on multiple verification points at a time).

•    Comparing large total of information is impractical (If nosotros wishing compare Thousands of
     Records, it is non possible, but Test Tool tin flaming compare thousands of records).

•    Checking relevance of search of functioning is difficult

•    Processing alter requests during software maintenance takes to a greater extent than time.

2)    Advantages of Test Automation
 

a)    Fast:
Automated tests are significantly faster than human users.

Test Tools are faster inwards Test execution than human users, In
two of import tasks,

i)    Test Design    ii)    Test Execution  Or Test Run

In instance of Test pattern Test Tools are non faster, for Test Design human user
interaction is mandatory. Test Tools supply IDE (Integrated Environment) for
designing Tests.

In instance of Test Execution Test Tools are faster than human users, Tool tin flaming execute serial of Tests chop-chop without user interaction.
Anyhow Test Design i fourth dimension activity but Test execution multiple times, then defiantly nosotros tin flaming relieve Time.

b)    Reliable
Tests perform just the same operations each fourth dimension they are run, thereby eliminating human error.
Human Users may brand mistakes, if you lot supply proper logic Test Tool tin flaming supply right output every time.

c)    Repeatable
We tin flaming attempt how the application reacts later repeated execution of the same operations.
We tin flaming execute same operations (Data Driven Testing) using multiple sets of Test Data. If it is manual Test Testing, takes to a greater extent than time.
 

Why nosotros demand to execute same operations multiple times?

For positive too Negative Testing nosotros perform Data Driven Testing.

d)    Programmable
We tin flaming programme sophisticated tests that convey out hidden information.
We tin flaming apply programming features to our tests (Ex: Flow command statements, Functions etc…) We tin flaming insert multiple verification points inwards an Automated Test, Test Tool is software it tin flaming concentrate on multiple verification points at a time, but inwards Manual testing human user tin flaming concentrate on i or ii verification points at a time, So  Automated Test range is really high than Manual Test case.

e)    Comprehensive
We tin flaming construct a suite of tests (Batch Testing) that covers every characteristic inwards our Application.
Software Test Tools back upwards Batch Testing (Executing Series of Tests), nosotros tin flaming practise attempt batches, without human user interaction Tools tin flaming execute attempt batches, if it is manual testing, each too every attempt instance execution user interaction is mandatory.

f)    Reusable
We tin flaming reuse tests on unlike versions of an application, fifty-fifty if the user interface changes.
Ex: Sanity Tests, Regression Tests

3)    Disadvantages of Test Automation
 

a) 100% attempt automation is impractical, to a greater extent than oftentimes than non nosotros crusade to automate maximum test
 scenarios.

b) All types of testing is non possible (Ex: Usability Testing)

c) More Efforts required at initial phase of Test Automation.

d) Not suitable dynamically changing UI designs

e) Debugging issues

f) Tools may cause got their ain defects, then nosotros may non drib dead desired benefits.

g)    Lack of knowledge

h)    Environment limitations (In UFT, if you lot wishing attempt Java Application Java Add inwards required, SAP Application SAP Add inwards required, UFT is non providing Add ins for All Environments.)
If it is manual testing no Environment limitations, irrespective of the Application Environment you lot tin flaming apply manual testing methods.
----------------------------------------
4) Types of Test Tools
 

a) Business classification

i) Vendor Tools
-----------------
Companies educate attempt tools for commercial use, license is required to usage too drib dead technical support.

HP- UFT, LoadRunner, QC/ALM etc…

IBM-Rational- Rational Robot, RFT, RPT, QA Director

Micro Focus-SilkTest, Silk Performer

ii) Open Source Tools

Source code available on NET anybody tin flaming download too use.

Ex: Selenium, Jmeter, Bugzilla, QAwebload etc…

iii) In-House Tools

Some companies educate attempt tools for their internal usage / Private use.
---------------------------------------------------------
b) Technical Classification
----------------------------
i) Functional & Regression Test tools
QTP, RFT, Selenium etc...

ii) Performance/Load/Stress Tools

 LR, RPT,Silk Performer JMeter etc

iii) Test management Tools

QC, QA Director etc...

iv) Defect Management Tools

Bugzilla, zera, Issue Tracker, PR-Tracker etc.

v) Security Test tools

vi) Unit Test tools Etc...
------------------------------------------------
5) Overview of Functional Testing
Verifying a cistron or systems functionality alongside honor to Functional
Requirements.

Coverage of Functional Testing

a) Input Domain Coverage
Verifying conditions the organization (Application nether Test) is accepting valid inputs
or not? And preventing invalid inputs or not?

b) Output Domain Coverage 


Verifying conditions the System is providing right Outputs or not, based on input too process

c) Database Testing
    Verifying the Data Integrity,

    Data Manipulations (Add, Edit, delete),       

    Data Processing,       

    Data Comparisons,       

    Data Back-up too Recovery Operations Etc...

d) Error handling
Verifying how the organization is treatment user unauthorized/invalid operations too providing error too assistance messages.

e) Order of functionalities
Verifying conditions the System is providing right guild of functionalities or not?
------------------------------------------------------

Sumber http://www.gcreddy.com/
Post a Comment (0)
Previous Post Next Post