testaro 14.6.0 → 14.6.2
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 +3 -0
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -154,6 +154,7 @@ Here is an example of a job:
|
|
|
154
154
|
batch: 'weborgs',
|
|
155
155
|
target: {
|
|
156
156
|
id: 'w3c',
|
|
157
|
+
which: 'https://www.w3c.org',
|
|
157
158
|
what: 'World Wide Web Consortium'
|
|
158
159
|
},
|
|
159
160
|
requester: 'user@domain.org'
|
|
@@ -271,6 +272,8 @@ standardResult: {
|
|
|
271
272
|
|
|
272
273
|
If a tool has the option to be used without itemization and is being so used, the `instances` array may be empty.
|
|
273
274
|
|
|
275
|
+
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.
|
|
276
|
+
|
|
274
277
|
### Acts
|
|
275
278
|
|
|
276
279
|
#### Introduction
|