This repo contains examples of a filtering tests for LeasePlan business showroom page.
Tools:
- webdriver.io@7
- mocha and built-in expect.
- CI: github actions, gitlab.
- reporting: allure, spec
- eslint with wdio-plugin.
- log4js for logging.
The following chart describes typical automation "framework" building blocks:
original file on a google drive
Key features:
- high-level, clear, readable, easy to understand, verbose specs. Contains only test logic (business cases). Do not contain any webdriver (other frameworks) calls and low-level methods.
- decoupled test logic, test data, and implementation (work with the browser, network, database, etc).
- services layer: expose only high-level methods (public API). Hide (encapsulate) all interaction with the driver, (ideally, for e2e tests) do not return web elements.
- easier to maintain and reuse code, e.g. service or UI component can update/change an internal login flow w/o affecting spec file.
- has rich UI components library: most of the widgets/components on frontend side should have representative class to use in automation. Complex components are built on top of the simple ones.
- Test should work on any linux/unix (CentOS, RedHat, Fedora, etc.) and Windows 10
- node.js version v14.15.5 (or higher)
node -v
v14.15.5- npm version 6.14.8. (package lock will be ignored with npm v less than 5)
npm -v
6.14.8Note: do not use npm 7+, it is still unstable and has some compatibility issues, e.g. package-lock breaking changes.
- optional, if you prefer to run selenium-standalone instead of chromedriver service:
- jdk11+, java also required to generate allure report locally.
- python3 and VSBuild tools since wdio works with fibers (will be installed during node.js installation). You should not do any additional installation with node14+, but if you get the following errors:
Follow the instructions to fix this.MSBUILD : error MSB3428: Could not load the Visual C++ component "VCBuild.exe". To fix this, 1) install the .NET Framework 2.0 SDK, 2) install Microsoft Visual Studio 2005 or 3) add the location of the component to the system path if it is installed elsewhere. Failed at the fibers@5.0.0 install script
- webdriver-manager,
run
webdriver-manager updateto get the latest versions of drivers
npm i -g webdriver-manager webdriver-manager update # status after update webdriver-manager status [18:05:42] I/status - selenium standalone version available: 3.141.59 [last] [18:05:42] I/status - chromedriver versions available: 84.0.4147.30, 85.0.4183.87, 86.0.4240.22, 87.0.4280.88, 88.0.4324.96 [last] [18:05:42] I/status - geckodriver versions available: v0.27.0, v0.29.0 [last] [18:05:42] I/status - IEDriverServer is not present [18:05:42] I/status - android-sdk is not present [18:05:42] I/status - appium is not present
cd wdio-js-demo/
npm i
# ...
npm t
# ...
npm run report
# ...
Report successfully generated to allure-report
Starting web server...
# ...
For automation engineer needs spec report is 100% enough, but to track statistics and for managers and other stakeholders I use industry-standard - Allure Report
!insert allure report!.
gitlab project, not stable yet.
!insert screenshots!
You can find more information about each run on Actions tab in github
- add allure steps.
We cannot mess up components methods with steps, so it should be a new Proxy object or "steps" module that wraps up all high-level calls.
see example in steps folder. - start selenoid on gitlab, instead of selenium standalone service.
- implement more UI components/widget: MonthlyPriceFilter, MoreFilters filter, etc.
- cleanup gitlab stages: start gitlab local runner and debug all the issues.
- gitlab: post results to allure server, use nginx or find another way to serve report.
- (minor) eslint default parser does not work with static properties, fix configuration with babel-parser.