chainwright 0.8.14 → 0.8.15
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 -3
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -182,7 +182,7 @@ export default defineWalletSetup(
|
|
|
182
182
|
Run setup with the CLI (Supports **npx**, **bun**, **pnpm**, and **yarn**):
|
|
183
183
|
|
|
184
184
|
>[!NOTE]
|
|
185
|
-
|
|
185
|
+
By default, Chainwright looks for `tests/wallet-setup` in your base directory. However, you can specify the directory you want Chainwright to get your setup files from.
|
|
186
186
|
|
|
187
187
|
```bash
|
|
188
188
|
bun chainwright --wallets <Wallets you want to support>
|
|
@@ -242,7 +242,7 @@ test.describe("Example tests", () => {
|
|
|
242
242
|
})
|
|
243
243
|
```
|
|
244
244
|
> [!NOTE]
|
|
245
|
-
|
|
245
|
+
The wallet fixture will make use of the `default` wallet profile. If you specified a `profile-name` at the point of setting up, make sure to include it in the fixture.
|
|
246
246
|
|
|
247
247
|
```ts
|
|
248
248
|
// No profile name is specified at setup time
|
|
@@ -314,7 +314,7 @@ Running Chainwright in CI is very similar to running Playwright in CI. The only
|
|
|
314
314
|
|
|
315
315
|
Why we make use of **xvfb**:
|
|
316
316
|
> [!IMPORTANT]
|
|
317
|
-
|
|
317
|
+
Browser extensions don't load in headless Chromium, so the tests have to run in headed mode. CI machines have no display, so launching a headed browser fails. xvfb provides a fake virtual display, letting Chromium run headed in CI as if a screen were attached.
|
|
318
318
|
|
|
319
319
|
```yml
|
|
320
320
|
name: CI
|
package/package.json
CHANGED