![Oracle Drags Its Feet in the JavaScript Trademark Dispute](https://cdn.sanity.io/images/cgdhsj6q/production/919c3b22c24f93884c548d60cbb338e819ff2435-1024x1024.webp?w=400&fit=max&auto=format)
Security News
Oracle Drags Its Feet in the JavaScript Trademark Dispute
Oracle seeks to dismiss fraud claims in the JavaScript trademark dispute, delaying the case and avoiding questions about its right to the name.
nightwatch-axe-core
Advanced tools
Nightwatch.js commands for running aXe-core.
Install using yarn or npm
npm install nightwatch-axe-core --save-dev
Add these commands to the custom_commands_path
in your Nightwatch.js configuration.
{
custom_commands_path : [
"./node_modules/nightwatch-axe-core/commands"
]
}
The axe()
command takes the following two parameters:
Parameter Name | Parameter Type | Description |
---|---|---|
context | string or object | css selector or include/exclude object |
options | object | set of axe options |
These can be defined globally and/or per call to the axe()
command.
In addition to the standard aXe options
:
options.timeout
configures Nightwatch's timeoutsAsyncScript()
amount, default value is 1000 milliseconds
.aXe can require a fair amount of time to run, so increasing the timeout
option is often required.
Injecting aXe-core
Since Nightwatch 2.3.6, axe is included by default, but still requires calling both axeInject()
and axeRun()
. This command handles both.
Create an axe.conf.js
file in your project root as an CommonJS module that exports a default object with both the
context
and options
parameters:
// axe.conf.js
module.exports = {
context: {
include: [['html']],
exclude: [['.advertising']],
},
options: {
runOnly: {
type: 'tag',
values: ['wcag2a', 'wcag2aa'],
},
timeout: 2000,
}
};
Then your test simply needs to call the axe()
command.
// nightwatch-test.js
export default {
'@tags': ['accessibility'],
'Thing passes aXe-core checks': function (browser) {
browser
.url(`${browser.launch_url}/page-to-test`)
.waitForElementPresent('.thing-to-test')
.axe()
.end()
}
}
When calling axe()
you can can pass in the context
and options
values as arguments. context
will override
any globally defined contexts, whilst options
will be merged with any globally defined options. This way you can
have edge case tests that inherit global config but can easily be change one or two things.
axe(context, options)
For example;
// nightwatch-test.js
export default {
'@tags': ['accessibility'],
'Thing passes aXe-core checks': function (browser) {
browser
.url(`${browser.launch_url}/page-to-test`)
.waitForElementPresent('.thing-to-test')
.axe('.thing-to-test', {
runOnly: {
type: 'tag',
values: ['wcag2a']
},
rules: {
'color-contrast': { enabled: true },
'valid-lang': { enabled: false }
},
})
.end()
}
}
When debugging a failure it can be useful to enable all of the output options, and set a large timeout;
options: {
timeout: 60000,
verbose: true,
selectors: true,
absolutePaths: true,
ancestry: true,
elementRef: true,
}
This will give you as much information as possible into what caused the failure.
Another helpful option is setting resultTypes: ['violations']
, as described in the
axe-core docs
which can improve performance and reduce timeout failures.
FAQs
Nightwatch.js commands for running aXe-core.
The npm package nightwatch-axe-core receives a total of 0 weekly downloads. As such, nightwatch-axe-core popularity was classified as not popular.
We found that nightwatch-axe-core demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 7 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Oracle seeks to dismiss fraud claims in the JavaScript trademark dispute, delaying the case and avoiding questions about its right to the name.
Security News
The Linux Foundation is warning open source developers that compliance with global sanctions is mandatory, highlighting legal risks and restrictions on contributions.
Security News
Maven Central now validates Sigstore signatures, making it easier for developers to verify the provenance of Java packages.