testaro 63.0.0 → 64.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 +4 -0
- package/package.json +1 -1
- package/run.js +0 -2
package/README.md
CHANGED
|
@@ -133,6 +133,10 @@ Once it is installed as a dependency, your application can use Testaro features
|
|
|
133
133
|
|
|
134
134
|
### Prerequisites
|
|
135
135
|
|
|
136
|
+
The host on which Testaro runs should have the latest long-term-support version of [Node.js](https://nodejs.org/en/).
|
|
137
|
+
|
|
138
|
+
Testaro is configured so that, when Playwright or Puppeteer launches a `chromium` browser, the browser is [sandboxed](https://www.geeksforgeeks.org/ethical-hacking/what-is-browser-sandboxing/) for improved security. That is the default for Playwright and Puppeteer, and Testaro does not override that default.Any host running Testaro must therefore permit sandboxed browsers. Documentation on how to configure an Ubuntu Linux host for this purpose is available in the [`SERVICE.md` file of the Kilotest repository](https://github.com/jrpool/kilotest/blob/main/SERVICE.md#browser-privileges). If you try to run Testaro on a host that prohibits sandboxed browsers, each attempted launch of a `chromium` browser will throw an error with a message complaining about the unavailability of a sandbox.
|
|
139
|
+
|
|
136
140
|
To make the Testaro features work, you will also need to provide the environment variables described below under “Environment variables”.
|
|
137
141
|
|
|
138
142
|
All of the tests that Testaro can perform are free of cost, except those performed by the WallyAX and WAVE tools. The owners of those tools issue API keys. A free initial allowance of usage may be granted to you with a new API key. Before using Testaro to perform their tests, get your API keys for [WallyAX](mailto:technology@wallyax.com) and [WAVE](https://wave.webaim.org/api/). Then use those API keys to define environment variables, as described below under “Environment variables”.
|
package/package.json
CHANGED
package/run.js
CHANGED
|
@@ -297,8 +297,6 @@ const launch = exports.launch = async (
|
|
|
297
297
|
);
|
|
298
298
|
if (headEmulation === 'high') {
|
|
299
299
|
browserOptionArgs.push(
|
|
300
|
-
'--no-sandbox',
|
|
301
|
-
'--disable-setuid-sandbox',
|
|
302
300
|
'--disable-gpu',
|
|
303
301
|
'--disable-software-rasterizer',
|
|
304
302
|
'--force-device-scale-factor=1',
|