-
Notifications
You must be signed in to change notification settings - Fork 68
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Axe core cli not working : Fails with "An error occurred while testing this page." #401
Comments
Thanks for reporting. I'll pass this along. Do you mind providing the dockerfile or environment? |
I'm experiencing this as well, trying to use axe locally on Linux:
(I get the same errors without the axe: 4.3.2 Let me know if there's more information I can provide to diagnose what's tripping axe up. |
Hey @rootwork, Could you please do the same test but add the flag Example: axe http://localhost:9050/ --verbose --show-errors axe https://codepen.io/rootwork/full/zYPwQbv --verbose --show-errors |
@Zidious Yep that looks like the issue:
|
If you could update your ChromeDriver version to 98. You may need to allow the ChromeDriver application in the firewall any try again. Edit: if the the above does not succeed, please try to pass the path of the ChromeDriver to the CLI tool: axe www.google.com --chromedriver-path /usr/local/bin/chromedriver I have opened a ticket to update the ChromeDriver dependencies to V98 which will follow up with a PR shortly. |
Seeing the same issue when chromedriver updated to 98. |
First just to be clear, I never installed ChromeDriver myself. I'm not sure if it comes with Chromium, axe, or my Linux distro, but I've definitely never downloaded it directly. I do see now that axe-core/cli's getting started says to install a webdriver, so I'm sorry for overlooking that. In any case,
Nonetheless, when I run
|
Oh and I meant to add, I get the same error when specifying the ChromeDriver path:
|
Hey @rootwork, Apologies for the delay, we recently merged a PR to fix the ChromeDriver issue (to use |
hi, I am trying to run axe tests with axe core via github actions. I tried to use npm i @axe-core/cli@4.4.1-alpha.247 -g below is the error i got. I have tried other versions as well. Either i get error stating axe command not found or the chrome driver does not work for the browser. This was working earlier with npm i @axe-core/cli@4.3.2-alpha.209 -g.
|
@mkathu Hey, as we are using the latest version of ChromeDriver, you will need to keep your Chrome Browser versions up to date. The error message you are receiving: Error: SessionNotCreatedError: session not created: This version of ChromeDriver only supports Chrome version 99
Current browser version is 98.0.4758.102 with binary path /usr/bin/google-chrome Means your Chrome browser is out of date. If you upgrade it v99 you should not have any issues |
Hi! I just wanted to chime in because I am also having issues with getting this tool to work in Github Actions. I am not trying to run this locally - I am running this in the virtual Github Actions environment. Does anyone have any tips on how to get this running? Here is the step in my yml file
Here's the results.
|
Hello all! it seems as though I have run into the same issue. Updated my chrome. it is chromedriver@100 being installed and it is still running this error. doesnt make a difference if i use the canary release command (npm i @axe-core/cli@4.4.1-alpha.247 -g) either. i even tried adding this action above it if anybody can shed some light- would be grateful !
|
Hey @shaquillaevelyn, The CLI is using the latest version of ChromeDriver at the moment it would be 100 upon installation. Your current chrome version is Alternatively, you can specify a specific version of ChromeDriver using |
Closing to due inactivity. Please re-open if issue is still apparent. |
Just ran into this issue while running in GitHub actions as @metalandcoffee, and I was able to fix it for my CI case. I had to force installing the correct version of both - name: Get Chromium version 🌐
run: |
CHROMIUM_VERSION=$(wget -qO- https://googlechromelabs.github.io/chrome-for-testing/LATEST_RELEASE_STABLE | cut -d. -f1)
echo "Chromium version: $CHROMIUM_VERSION"
echo "CHROMIUM_VERSION=$CHROMIUM_VERSION" >> $GITHUB_ENV
- name: Setup Chrome 🌐
id: setup-chrome
uses: browser-actions/setup-chrome@v1
with:
chrome-version: ${{ env.CHROMIUM_VERSION }}
- name: Install chromedriver 🚗
run: |
npm install -g chromedriver@$CHROMIUM_VERSION
- name: Run axe 🪓
# https://github.com/dequelabs/axe-core-npm/tree/develop/packages/cli
run: |
npm install -g @axe-core/cli
npm install -g http-server
http-server _site/ &
axe --chromedriver-path $(npm root -g)/chromedriver/bin/chromedriver http://localhost:8080/ --load-delay=1500 --exit |
@george-gca I'm getting error as " Error: Error: Server terminated early with status 127 I forceinstalled the latest versions of Chromium and Chrome driver. Chromium version is 121 ..Node version: 18 |
The chromedriver library updates more frequently than the chrome distributed in ubuntu-latest, but these need to be the same version, otherwise axe-core breaks. As a workaround, try to install a version that matches whatever chrome is on the path. See also dequelabs/axe-core-npm#401 (comment)
The chromedriver library updates more frequently than the chrome distributed in ubuntu-latest, but these need to be the same version, otherwise axe-core breaks. As a workaround, try to install a version that matches whatever chrome is on the path. See also dequelabs/axe-core-npm#401 (comment)
* update form with updated fields * update form with updated fields * implement custom property search * update pre-commit - add sync_with_poetry hook to keep pre-commit in sync with pyproject.toml - config flake8 - config isort to use black via pyproject.toml Add .secrets.baseline for detect-secrets move testing libraries to dev.dependencies in pyproject.toml * linting * linting and formatting for readability * revert domains (plural) -> domain (singular) changes (may be implemented in later PR) * add descriptions and code annotations for added helper functions add default for dict.get() [linting] * keep original indent for domain filters * linting * add pre-commit instructions/details to readme * Changed value for selection option an empty string and updated where_to_access choice value to 'Analytical_Platform' to avoid spaces. q exit quit() q ��[200~classifications~classifications * Make domain a single choice field * Removed admin.py as not required * Moved filter code to new partial template * refactor domain and subdomain choices to get the urn value * build filter strings method to create filter search strings * refactor classifications and where to access string generation, remove full query builder * refactor where to access href creation * add get_keys and format_label template filter functions * Update broken tests * add selected filters partial * update packages * refactor encode_without_filter function * remove redundant code * update tests with singular domain, classifications and where_to_access * Update dingular domain and add linting fixes * linter updates * add service for dataproductdetails * update templates - data product details and search * url for search link and details redirect in views * add tests for data product details and view * add selenium test for data product detail page * update poetry * fix selenium tests that sometimes hit a dead end * actually make the tests work for data product details * this template will always be data product and align case * rename view, service and add blank dataset template * markdown and trim for table descriptions in data product detail page * remove self.data_product_name from dataproductservice * try reinstalling deps for selenium tests * revert workflow change * Add javascript for domain filter widget Domain will have top level and subdomain selections, and work similarly to "Topic/Sub-Topic" on GOV.UK search. The form will submit domain and subdomain as separate fields, so we need to combine them on the backend. If javascript is not enabled, then the subdomain field is not displayed and it will work as before. This is tested using jest and jest-dom. * Revert template - will add backend later * Add test * Install a compatable version of chrome/chromedriver The chromedriver library updates more frequently than the chrome distributed in ubuntu-latest, but these need to be the same version, otherwise axe-core breaks. As a workaround, try to install a version that matches whatever chrome is on the path. See also dequelabs/axe-core-npm#401 (comment) * update form with updated fields * update form with updated fields * implement custom property search * revert domains (plural) -> domain (singular) changes (may be implemented in later PR) * Make domain a single choice field * refactor classifications and where to access string generation, remove full query builder * refactor where to access href creation * update packages * linter updates * remove duplicated function * update search result ui fields * fix result type in conftest * remove official-sensitive classification * add Custom Properties match display and rename 'list' to value_list --------- Co-authored-by: Tom Webber <thomas.webber@digital.justice.gov.uk> Co-authored-by: LavMatt <mattlaverty@gmail.com> Co-authored-by: Mat Moore <MatMoore@users.noreply.github.com>
As part of CI/CD I am trying to use axe-core/cli to scan couple of pages via github actions workflow. The steps were working earlier but not it fails with error. Below is the workflow and screenshot of the logs.
Product: axe-core/cli
Expectation: The github workflow should be able to execute and scan all the URL's specified.
Actual: The execution fails.
Motivation: Disables the usage in CI/CD
axe-core/cli version: 4.3.1
axe-core version 4.3.5
The text was updated successfully, but these errors were encountered: