Phases of Software Test Process or Software Test Life Cycle
1) Test Planning
2) Generating Basic Tests
3) Enhancing Tests
4) Running & Debugging Tests
5) Analyzing Test Results as well as Reporting Defects
----------------------------------------
1) Test Planning
> Get Application Environment (UI pattern as well as Database) details from evolution team
> Analyze the AUT inwards damage of Objects/Elements Identification
Using Recording characteristic inwards Selenium IDE
Or
Using Element Inspectors nosotros tin inspect Elements.
Mozilla Firefox - Page Inspector
Chrome or IE - Developer Tools
> Select Test Cases for Automation
Test Cases that nosotros convey to execute on every software get (Sanity Tests)
Test Cases that nosotros convey to execute on every modified software get (Regression Tests)
Test Cases that nosotros convey to execute using multiple sets of Test information (Data Driven Tests)
> Choose Selenium Tools as well as Configure
----------------------------------------
2) Generating Basic Tests
In UFT/QTP
1) Object Repository based Test Design (Recording, keyword driven methodology)
2) Descriptive Programming / programmatic Descriptions
In Selenium:
Selenium IDE:
a) Using Recording
Or
b) Type Test steps using Element Locators as well as Selenese Commands
Selenium WebDriver
Using Element Locators as well as WebDriver Commands / Methods
----------------------------------------
3) Enhancing Tests
i) Inserting Verification Points
In UFT/QTP
Using UFT Checkpoints or VBScript Conditional Statements
In Selenium
Selenium IDE
Using Assert / Verify Commands
Selenium WebDriver
Using Java Flow Control Statements (Conditional)
Or
Using Testing Framework (JUnit / TestNG) Assertion Methods
----------------------------------------------------
ii) Parameterization
Replacing constant (fixed) values amongst Parameters (ex: variables)
Purpose of Parameterization
To conk unmarried value (When nosotros telephone phone user defined methods)
To conk multiple values (To comport Data Driven Testing)
What is Data Driven Testing?
Testing the same functionality using multiple sets of Test Data.
Why Data Driven Testing?
For Positive as well as Negative Testing
Relation betwixt Parameterization as well as Data Driven Testing
We usage Parameterization characteristic inwards Data Driven Testing
In UFT / QTP
Using UFT Tool characteristic Data Table or yesteryear importing External files (Test information file)
Selenium IDE
Selenium IDE doesn't back upward Parameterization
Selenium WebDriver
By importing External files (Test information file) nosotros tin Parameterize Test cases
----------------------------------------------------
iii) Synchronization
What is Synchronization?
Why Synchronization?
How to Synchronize Selenium as well as AUT?
Using WebDriver Command or Java Method
----------------------------------------------------
iv) Error Handling
Handling expected as well as unexpected errors
In UFT:
Using Recovery Scenarios or VBScript features
In Selenium WebDriver
Using Java Exception handling
v) Adding Comments (Optional)
To brand the code readable
To brand the code disable from execution
Etc...
-------------------------------------------
4) Running & Debugging Tests
Running ......
Running - Debugging - Running....
----------------------------------
Running / Execution
Types of Test Run
1) Single Test Run
2) Batch Testing
You tin write &execute multiple exam cases inwards a Java Class
Or
Using Testing Framework (JUnit/TestNG)
---------------------------------
Debugging Test Cases (Optional)
What is debugging?
Locating as well as isolating errors through stride yesteryear stride execution
When Debugging is required?
Scenario 1: Test Case is non showing whatever errors as well as providing right output - Not required
Scenario 2: Test Case is showing errors- Debugging optional
Scenario 3: Test Case is non showing whatever errors as well as Not providing right output - Required
----------------------------------------------------------------
5) Analyze Test Results as well as Reporting Defects
Analyze Test Results
Selenium IDE provides Test Result (Summary only) for every Test Iteration.
Selenium WebDriver doesn't convey Reporting facility
Using Java Programming nosotros tin define Test Results
Or
Using Testing Framework (JUnit/TestNG) nosotros tin generate Test Reports.
----------------------------------------------
Status of Test Results inwards Functional Test Automation
1) Pass (if Expected = Actual)
2) Fail (if Expected != Actual)
3) Done (if in that place is no verification indicate inwards the Test Case)
4) Warning (if whatever intermission during exam execution)
-------------------------------------------
Reporting Defects
No Tool Integration amongst Selenium for Test Management / Defect Management
Functional Test Automation Defect Management
-----------------------------------------------------------------------------
Selenium Manual
------------------------------------------------------------------------------
Selenium Bugzilla / Jira etc...
--------------------------------------------------------------------------------