-
Notifications
You must be signed in to change notification settings - Fork 42
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: add synthetics script generator #375
feat: add synthetics script generator #375
Conversation
❕ Build Aborted
Expand to view the summary
Build stats
Test stats 🧪
Trends 🧪Log outputExpand to view the last 100 lines of log output
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just had a few questions and some nit typo corrections. I've walked through this and based on the test outputs and the code itself I haven't found any major concerns.
LGTM
formatter.add(` | ||
const { journey, step, expect } = require('@elastic/synthetics'); | ||
|
||
journey('Recorded journey', async ({ page, context }) => {`); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Will it ever be useful to take a param for the journey name?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not for the current iteration. We dont have any option of passing down params from recording, but definitely in future.
Note: Only exception is the use of assertion IR which is different from PW actions which does not have the capability yet.