Selenium Test Automation Framework

The Framework is best suited for Smoke, Acceptance and Regression functional tests.It represents good structured logging and reporting which can be used as test documentation even for manual test team. It is possible to see high-level user functional actions (can be used as test-case documentation) and also low-level debug information. Error handling helps to see the reasons of test fails. It includes the error message, stack-trace and screen capture of browser window.

For complicated test-cases several browsers can be run in parallel. E.g. chat or whiteboard tests.

Advantages & Disadvantages

Pros: use and execution

1. Good integration with CI

2. Supports cross-browser testing

3. Supports multiconfiguration run

4. Supports parallel run

5. Good structure for smoke, acceptance, regression, end-to-end functional tests

6. Good results representation: reports, logs, screenshots, video capture

7. Used extended test results statuses: PASSED, FAILED, STOPPED, SKIPPED

Pros: test development

1. Uses groovy script language with JAVA

2. Uses Page Object approach with DSL

3. Framework logic and Tests logic are separated

4. Ability to run several browsers in parallel and check their interactions (e. g. online chat tests)

5. Ability to check none-html objects and UI changes via Image comparator

6. Easy to analyze test results, advanced error handling approach implemented, separation of test fails on assert (FAILED) and any other error(STOPPED)

7. Ability to record video of tests execution - easy to analyze bugs and problems

Cons: test development

1. Test cases and suites bodies have fixed structure, deviations not recommended

2. Limitation to use only XPATH locators for WebElements

How it helps to speedup delivery/improve quality?

If the project is long-term (a year or more) automation

1. It saves significant time for regression and cross-browser testing, which QA is forced to conduct each iteration

2. Makes it possible to automatically fill in content with an application for manual testing

3. Eliminates the human factor when performing automated tests

4. Allows QA to concentrate on new functionality and bottlenecks, leaving the already proven features - automation

After completion of the project, the customer receives the following features

1. Run test packages with one click of the mouse without the involvement of specialists

2. Check that the existing functionality works after changes in the application code / configuration

3. Measure application performance by analyzing test suite run times

4. Timely eliminate defects because Autotests can be run regularly and at any time. Including how to delay start at night

5. Test suites will be a source of knowledge because by them you can understand how the application works