https://github.com/applitools/applitools-webdriverio-githubactions
https://github.com/applitools/applitools-webdriverio-githubactions
Last synced: 21 days ago
JSON representation
- Host: GitHub
- URL: https://github.com/applitools/applitools-webdriverio-githubactions
- Owner: applitools
- Created: 2021-04-14T09:28:07.000Z (about 5 years ago)
- Default Branch: main
- Last Pushed: 2021-04-14T14:16:00.000Z (about 5 years ago)
- Last Synced: 2025-01-17T04:47:36.675Z (over 1 year ago)
- Language: JavaScript
- Size: 63.5 KB
- Stars: 1
- Watchers: 3
- Forks: 0
- Open Issues: 1
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# Applitools-Wedriverio-Hackathon
## Pre-Requisites
1. Install ChromeDriver from [here](https://chromedriver.chromium.org/downloads) if you are running on mac, you can also install it using the brew,
simply run ```brew install chromedriver```
- Please check to make sure your google chrome browser is the same version as the chromedriver you install
1) Open chrome and navigate to chrome://settings/help
2) Check your version!
1) Download the compatible chriomeDriver version: [here](https://chromedriver.chromium.org/downloads)
2. Register to Applitools and [create an account](https://auth.applitools.com/users/register)
3. Ensure you have your Applitools API Key
## Hackathon Overview
Imagine you wrote tests for the [1st Version of the App (V1)](https://demo.applitools.com/hackathon.html)
Then Next [Version (V2)](https://demo.applitools.com/hackathonV2.html) came along later and has changes. (including bugs)
Some of these bugs are functional bugs, and some of are visual bugs.
### The Challenge
Write an automated test for both versions which leverages Applitools.
Run both a traditional test (provided), and the new test you wrote.
Compare the results.
### Instructions
1) Review Traditional Script (provided)
TraditionalTestSuite has been provided to you, as we assume you have already written these scripts before.
Analyze them, make sure they are ok, and feel free to add any additional coverage/lines of code you see fit.
2) Run the test suite against both Version 1 and Version 2.
You are going to find a lot of failures in Version 2. (changes have been made, including bugs)
3) Review the scripts again, and review how many assertions and locators required to cover all the elements in the page.
4) Open the VisualAISuite and set your ApiKey in string 'conf.setApiKey("...")' (or comment the string and set APPLITOOLS_API_KEY environment variable).
5) Run the same test again and see all the differences between the screenshots of the 1st version and the 2nd version of the app.
Note: When you run the tests against V2, you’ll see differences in screenshots because the app is actually different.
You should see exactly what those differences are (highlighted in pink) in Applitools dashboard.
## Running the example:
1. Download the example
* Option 1: `git clone https://github.com/applitools/Applitools-Webdriverio-Hackathon.git`
* Option 2: Download it as a Zip file and extract it
2. Run the Project inside Visual Studio Code
### In order to run the tests from commandLine:
1. Open a commandLine window
2. Navigate to the recently cloned folder Applitools-WDIO-Hackathon.
3. `npm ci` or `yarn install`
4. Run one of the following commands from the terminal:
Run the Traditional Test Suite on Version 1
- npm run TraditionalTestSuiteV1
Run the Traditional Test Suite on Version 2
- npm run TraditionalTestSuiteV2
Run the VisualAISuite Test Suite on Version 1
- npm run VisualAISuiteV1
Run the VisualAISuite Test Suite on Version 2
- npm run VisualAISuiteV2
## To see the full solution
Run the VisualAISuiteFullSolution Test Suite on Version 1
- npm run VisualAISuiteSolutionV1
Run the VisualAISuiteFullSolution Test Suite on Version 2
- npm run VisualAISuiteSolutionV2