From d74c63ab52b5fc94272969622d8fbbf96bcf1a16 Mon Sep 17 00:00:00 2001 From: j-mendez Date: Thu, 8 Feb 2024 21:39:41 -0500 Subject: [PATCH] chore(test): fix extension usage --- README.md | 2 -- kayle/tests/extension.ts | 1 + 2 files changed, 1 insertion(+), 2 deletions(-) diff --git a/README.md b/README.md index 91b5d9d5..7d1c3d84 100644 --- a/README.md +++ b/README.md @@ -205,8 +205,6 @@ Currently `fast_htmlcs` runs around 50x faster than axe-core and has several dif If you use [`@playwright/axe-core`](https://playwright.dev/docs/next/accessibility-testing) you can swap it out with the following [playwright-axe-example](./kayle/tests/basic-axe-playwright.spec.ts) and get an increase in issues found and major performance boost of at least 100%. You can also include multiple runners to extend the issues beyond the basics in folds. -We have not tested IBM Ace for performance thoroughly yet but, from the surface the performance is about 40% slower than axe, if the runner seems to have issues we may fork it and add it to the `fast_` prefix. The perf drawbacks may be from the lib handling all locales in one script. - ## Performance Tips As we set the foundation to mark test cases that can pass and increase our target on automating accessibility we have a couple of layers that can make a major difference to the project. The following will save drastic time and money if done. diff --git a/kayle/tests/extension.ts b/kayle/tests/extension.ts index 3c574455..284e82b4 100644 --- a/kayle/tests/extension.ts +++ b/kayle/tests/extension.ts @@ -11,6 +11,7 @@ import { performance } from "perf_hooks"; const ext = join(cwd(), "chrome-extension"); const browser = await puppeteer.launch({ + headless: "new", dumpio: true, ignoreDefaultArgs: ["--disable-extensions"], args: [