Selenium Test Process

Selenium Test Process

Phases of Software (Manual) Test Process/STLC    

    I) Test Planning
    II) Test Design
    III) Test Execution
    IV) Test Closure  
-----------------------------
Phases of UFT / QTP Test Process    

    I) Planning
    II) Generating Basic Tests
    III) Enhancing Tests
    IV) Running in addition to Debugging Tests
    V) Analyzing Test Results
    VI) Reporting Defects
----------------------------
Selenium Test Process
 

Phase I: Test Planning
 

> Get Application Environment details (UI design, in addition to Database) from evolution squad

> Analyze the AUT inwards price of UI elements Identification

        Using Selenium IDE Recording feature
        Or
        Using Firebug in addition to Firepath (They tin sack hold out used to inspect UI elements)


> Select Test cases for Automation

    Tests that nosotros convey to execute on every construct (Sanity tests)
    Tests that nosotros convey to execute on every modified build(Regression Tests)
    Tests that nosotros convey execute using multiple sets of Test information (Data Driven Tests)

> Select Framework (TestNg) in addition to configure
-----------------------------------------------
Phase II) Generating Basic Tests
 

In UFT:
a) Object Repository based Test Design (Recording, Keyword driven methodology)

b) Descriptive Programming (Static, Dynamic Programming)
--------------------
In Selenium:
a) Using Recording characteristic inwards Selenium IDE Or Type Test scripts using UI elements locators in addition to Selenium commands

b) Write Test scripts using UI elements locators inwards Selenium RC(Out dated)

c) Write Test scripts using UI elements locates in addition to WebDriver Methods inwards WebDriver interface.

Note: In Selenium no object Repository, in addition to thus no centralized maintenance of Objects/UI Elements

Phase III : Enhancing Test Cases
 

Insert Verification points

Add comments

Parameterization

Synchronization

Working amongst files

Error handling

Etc...
-----------------------
IV) Running in addition to Debugging Test Cases
 

Single Test Run

Batch Testing
    Using JUnit or TestNg frameworks nosotros tin sack execute Test batches

Debugging Tests

> Locating in addition to Isolating Errors thru stride yesteryear stride execution

> Debugging is non required for all tests.

> Whenever Test is non showing whatever errors in addition to non providing right output

V) Analyzing Test Result


 Status of Test Result inwards Functional Test Automation

Pass (If expected number = Actual Result)

Fail (If expected number <> Actual Result)

Done (Test execution without errors, No verifications)

Warning (Interruption during exam execution)

Define Test Result:

WebDriver doesn't convey whatever Built-in Test study generator

Using programmatic statements nosotros tin sack generate exam Results

Using TestNg nosotros tin sack generate Test Reports

VI) Reporting Defects
 

Functional Test Automation        Defect Management
---------------------------------------------------------
Selenium                                 Manual (No tool support)
---------------------------------------------------------------
Selenium                                 Bugzilla or whatever Tool
------------------------------------------------------------

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