testaro 14.5.1 → 14.6.1

package/README.md

@@ -271,6 +271,8 @@ standardResult: {
 
 If a tool has the option to be used without itemization and is being so used, the `instances` array may be empty.
 
+The standard format is not opinionated about issue classifications. It treats an issue ID from any tool as an identifier of what that tool considers to be the issue. Useful reporting from multi-tool testing still requires issue classification. If tool `A` identifies an issue as `alt-incomplete` and tool `B` identifies an issue as `image_alt_meaningless`, Testaro does not decide whether those are really the same issue or different issues. That decision belongs to whoever consumes Testaro reports. The standardization of tool reports by Testaro eliminates some of the drudgery in issue classification, but not any of the judgment required for issue classification.
+
 ### Acts
 
 #### Introduction
@@ -532,7 +534,7 @@ The `ibm` tool is one of two tools (`testaro` is the other) with a `withItems` p
 
 The `nuVal` tool performs the tests of the Nu Html Checker.
 
-Its `rules` argument is **not** an array of rule IDs, but instead is an array of rule _specifications_. A rule specification for `nuVal` is a string with the format `type:substring`, where `type` is replaced with a message type (namely `info` or `error`) and `substring` is replaced with any substring of a message. This `rules` format arises from the fact that `nuVal` generates customized messages and does not accompany them with rule identifiers. Thus, by choosing a type and a substring, you are deciding that any message of that type that includes that substring will be deemed a `nuVal` rule.
+Its `rules` argument is **not** an array of rule IDs, but instead is an array of rule _specifications_. A rule specification for `nuVal` is a string with the format `=ruleID` or `~ruleID`. The `=` prefix indicates that the rule ID is invariable. The `~` prefix indicates that the rule ID is variable, in which case the `ruleID` part of the specification is a matching regular expression, rather than the exact text of a message. This `rules` format arises from the fact that `nuVal` generates customized messages and does not accompany them with rule identifiers.
 
 ###### QualWeb
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "testaro",
-  "version": "14.5.1",
+  "version": "14.6.1",
   "description": "Automation of accessibility testing",
   "main": "index.js",
   "scripts": {

package/tests/nuVal.js

@@ -60,17 +60,24 @@ exports.reporter = async (page, options) => {
       fetchOptions.body = page[1];
       const nuResult = await fetch(nuURL, fetchOptions);
       const nuData = await nuResult.json();
-      const nuDataClean = JSON.parse(JSON.stringify(nuData).replace(/[\u{fffd}“”]/ug, ''));
       // Delete left and right quotation marks and their erratic invalid replacements.
+      const nuDataClean = JSON.parse(JSON.stringify(nuData).replace(/[\u{fffd}“”]/ug, ''));
       data[page[0]] = nuDataClean;
-      // If there is a report and restrictions on the report messages were specified:
+      // If there is a report and rules were specified:
       if (! data[page[0]].error && rules && Array.isArray(rules) && rules.length) {
         // Remove all messages except those specified.
-        const ruleSpecs = rules.map(ruleSpec => ruleSpec.split(':', 2));
-        data[page[0]].messages = data[page[0]].messages.filter(message => ruleSpecs.some(
-          ruleSpec => message.type === ruleSpec[0]
-          && message.message.includes(ruleSpec[1])
-        ));
+        data[page[0]].messages = data[page[0]].messages.filter(message => rules.some(rule => {
+          if (rule[0] === '=') {
+            return message.message === rule.slice(1);
+          }
+          else if (rule[0] === '~') {
+            return new RegExp(rule.slice(1)).test(message.message);
+          }
+          else {
+            console.log(`ERROR: Invalid nuVal rule ${rule}`);
+            return false;
+          }
+        }));
       }
     }
     catch (error) {