testaro 18.13.2 → 18.13.3
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +2 -0
- package/package.json +1 -1
- /package/{testaro → data}/template.js +0 -0
package/README.md
CHANGED
|
@@ -565,6 +565,8 @@ The `testaro` tool (like the `ibm` tool) has a `withItems` property. If you set
|
|
|
565
565
|
|
|
566
566
|
Unlike any other tool, the `testaro` tools requires a `stopOnFail` property, which specifies whether a failure to conform to any rule (i.e. any value of `totals` other than `[0, 0, 0, 0]`) should terminate the execution of tests for the remaining rules.
|
|
567
567
|
|
|
568
|
+
You can add custom rules to the rules of any tool. Testaro provides a template, `data/template.js`, for the definition of a rule to be added. Once you have created a copy of the template with revisions, you can move the copy into the `testaro` directory and add an entry for your custom rule to the `evalRules` object in the `tests/testaro.js` file. Then your custom rule will act as a Testaro rule.
|
|
569
|
+
|
|
568
570
|
###### WAVE
|
|
569
571
|
|
|
570
572
|
If a `wave` test act is included in the job, an environment variable named `WAVE_KEY` must exist, with your WAVE API key as its value. You can get it from [WebAIM](https://wave.webaim.org/api/).
|
package/package.json
CHANGED
|
File without changes
|