Selenium Test Process

Test Planning

Get environment details (UI design and database) from development team.
Analyse the AUT (application under test) in terms of object identification/element identification.
Select test cases for automation
1 ) Test cases that can be executed on initial build and every modified build i.e. Smoke, Sanity.
2) Test cases that can be executed on every modified build (regression tests).
3) Test cases that can be executed using multiple sets of test data (Data driven).
Select selenium tools and others for automated testing and configure Eclipse IDE, Java, Selenium Webdriver, TestNG, Maven, Jenkins etc..

Generate basic test cases

Creating normal steps or creating plane navigation using element locators and webdriver API commands.

Enhance test cases

Inserting Verification: Using “verify” or “asserts” commands
Parametarization: Replacing constant values with parameter is called parametarization using (flat file,Excel etc..)
Synchronization: Using programming wait feature on webdriver commands.
Error Handling: Handling expected and unexpected errors using programming features (Exception handling in Java)
Adding Comments

Run and Debug test cases

Run > Debug > Run
Run/Execute test cases is a mandatory task in testing, but debugging test cases is an optional task in automated testing. In Selenium we execute test cases using testing framework.
Debug test cases is NA for manual testing and It is used only in automated testing.
(Debugging is locating and isolating errors throw step by step execution)

Analyze test results and report defects

Analyze test results using programming control flow statements or testing framework verification methods.
Status of test results in automation testing:
1) Pass (if expected == actual)
2) Fail (if expected != actual)
3) Done (if there is no verification point in test cases)
4) Warning (Whenever a test cases is not executing property)
Report Defects, After analyzing the test results if we find any deviation from expected then report defects.