testilo 9.0.1 → 9.0.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 -14
- package/call.js +1 -1
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -11,18 +11,6 @@ Testaro performs digital accessibility tests on web artifacts and creates report
|
|
|
11
11
|
|
|
12
12
|
Because Testilo supports Testaro, this `README` file presumes that you have access to the Testaro `README` file and therefore does not repeat information provided there.
|
|
13
13
|
|
|
14
|
-
## Branches
|
|
15
|
-
|
|
16
|
-
The `writer` branch contains the state of Testilo as of 2022-11-07. In that branch, Testilo must read and write files. That makes Testilo unusable as a dependency in applications that do not have permission to both read and write files.
|
|
17
|
-
|
|
18
|
-
The `simple` branch contains the state of Testilo as of 2022-12-23. In that branch, Testilo does not need to read or write files, so applications without write permission can still use Testilo as a dependency.
|
|
19
|
-
|
|
20
|
-
The `main` branch contains the state of Testilo from 2022-12-24 until now. In that branch, Testilo can prepare jobs that require multi-step operations to reach and pre-process the targets being tested.
|
|
21
|
-
|
|
22
|
-
The `complexmerge` branch refactors `main` and is to be merged into `main` when the refactoring is complete.
|
|
23
|
-
|
|
24
|
-
This `README.md` file documents the `complexmerge` branch and will document the `main` branch when `complexmerge` is merged into `main`.
|
|
25
|
-
|
|
26
14
|
## Dependencies
|
|
27
15
|
|
|
28
16
|
The `dotenv` dependency lets you set environment variables in an untracked `.env` file. This prevents secret data, such as passwords, from being shared as part of this package.
|
|
@@ -110,7 +98,7 @@ Suppose you have created this script:
|
|
|
110
98
|
}
|
|
111
99
|
```
|
|
112
100
|
|
|
113
|
-
The `acts` array of this script contains
|
|
101
|
+
The `acts` array of this script contains three regular acts and two placeholders.
|
|
114
102
|
|
|
115
103
|
#### Batch
|
|
116
104
|
|
|
@@ -343,7 +331,7 @@ node call score sp25a 75
|
|
|
343
331
|
```
|
|
344
332
|
|
|
345
333
|
When a user invokes `score` in this example, the `call` module:
|
|
346
|
-
- gets the scoring module `sp25a` from its JSON file `sp25a.json` in the `process.env.
|
|
334
|
+
- gets the scoring module `sp25a` from its JSON file `sp25a.json` in the `score` subdirectory of the `process.env.FUNCTIONDIR` directory
|
|
347
335
|
- gets the reports from the r`raw` subdirectory of the `process.env.REPORTDIR` directory
|
|
348
336
|
- writes the scored reports to the `scored` subdirectory of the `process.env.REPORTDIR` directory
|
|
349
337
|
|
package/call.js
CHANGED
|
@@ -75,7 +75,7 @@ const getReports = async (type, selector = '') => {
|
|
|
75
75
|
// Fulfills a scoring request.
|
|
76
76
|
const callScore = async (scorerID, selector = '') => {
|
|
77
77
|
// Get the raw reports to be scored.
|
|
78
|
-
const reports = getReports('raw', selector);
|
|
78
|
+
const reports = await getReports('raw', selector);
|
|
79
79
|
// If any exist:
|
|
80
80
|
if (reports.length) {
|
|
81
81
|
// Get the scorer.
|