test[e2e]: Add PlanX input components to create-flow test #3617
Conversation
|
Removed vultr server and associated DNS entries |
jamdelion
changed the title
There was a problem hiding this comment.
Minor toast improvements cherry-picked from the react-toastify PR so it's not forgotten :)
| import { Browser, Page, Request } from "@playwright/test"; | ||
| import { createAuthenticatedSession } from "../globalHelpers"; | ||
|
|
||
| export const isGetUserRequest = (req: Request) => | ||
| req.url().includes("/user/me"); |
There was a problem hiding this comment.
Renamed the file to be more specific to 'getPage' helpers, and moved this to another file
There was a problem hiding this comment.
Just moved this file into a helpers folder and moved a couple of the functions into another file with a better name
There was a problem hiding this comment.
Sorry there's a lot of changes like this where it's just the imports that have changed!
jamdelion
changed the title
| 1. Navigate to `/tests/ui-driven` | ||
| 2. Run `pnpm install` to install the Playwright package. | ||
| 3. Run `pnpm exec playwright install` to install the Playwright test browsers. | ||
| 4. Run the tests with `pnpm test` |
| noBranchNoticeText, | ||
| ); | ||
|
|
||
| // TODO: find a nicer way to find the next node |
There was a problem hiding this comment.
When you're in a real browser, a handy trick for doing this is running window.api.getState().upcomingCardIds() in the console - where the next node ID will be the first item in the returned array. From there, you can do flow[nodeId] for the full node data like its' type etc.
Just flagging in case it jogs any future ideas ! setFeatureFlag & getSessionId helper functions already hook into similar window calls, so might be a pattern we can follow here too!
| await page.getByRole("dialog").waitFor(); | ||
| await page.locator("select").selectOption({ label: type }); | ||
|
|
||
| switch (type) { |
Trello ticket: https://trello.com/c/dBmTyu9F/3017-test-each-planx-component-via-an-e2e-test
So far I've just focused on adding in the relatively easy 'input' components. The next PR will start to tackle the more complicated ones.
In this PR:
useToasthook improvement cherry-picked from my closed react-toastify PR 🍒