testaro 44.0.0 → 45.0.0
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 -2
- package/package.json +1 -1
- package/run-main.js +0 -1405
package/README.md
CHANGED
|
@@ -153,7 +153,6 @@ Here is an example of a job:
|
|
|
153
153
|
}
|
|
154
154
|
},
|
|
155
155
|
browserID: 'webkit',
|
|
156
|
-
lowMotion: false,
|
|
157
156
|
timeLimit: 80,
|
|
158
157
|
creationTimeStamp: '241229T0537',
|
|
159
158
|
executionTimeStamp: '250110T1200',
|
|
@@ -876,7 +875,9 @@ The rationales motivating the Testaro-defined tests can be found in comments wit
|
|
|
876
875
|
|
|
877
876
|
### Abnormal termination
|
|
878
877
|
|
|
879
|
-
On
|
|
878
|
+
On some occasions a test throws an error that cannot be handled with a `try`-`catch` structure. It has been observed, for example, that the `ibm` test does this when the page content, rather than the page URL, is given to `getCompliance()` and the target is `https://globalsolutions.org` or `https://monsido.com`.
|
|
879
|
+
|
|
880
|
+
Some tools take apparently infinite time to perform their tests on some pages. To handle such stalling, Testaro subjects most tools to time limits. Further testing will be required before it can be determined whether this time limitation is robust. As currently implemented (without child processes), it may allow tool testing processes to continue and to write indefinitely to the response.
|
|
880
881
|
|
|
881
882
|
### Activation
|
|
882
883
|
|