-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
[DOCS-9465] adding Synthetics templates #26462
Conversation
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.
Hey Alicia, just one thing I was wondering about - looks awesome otherwise!
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.
Hey Alicia! I made some comments about structure, so we can try and make it as clear as possible when users must perform a step vs. where they decide to do one or more steps instead of others. Don't hesitate to let me know if you have any questions!
Hi @janine-c this is ready for a full review! Thank you for the great feedback :) |
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.
Looks great, Alicia! I know it looks like I made a ton of comments, but it's really just the same couple of points over and over that I wanted to help you spot (if you do decide to address them) because there's so much content and it's easy to miss things when the feedback is repetitive.
A couple of other minor things I spotted throughout that are low-stakes and that you don't have to deal with now:
- I noticed some inconsistent spacing when referring to buttons that started with a
+
- for example, +Add thing vs. + Add thing. I like the space because it's easier to read and mimics the UI better, but it's not the end of the world if it stays in there. - When a step is optional, I like to indicate that at the beginning of the step - it makes it a lot easier for a user to scan through and quickly decide whether they need to read that step (for example, if they want to just set something up quickly to get themselves unblocked) or if they can skip it. It can add some cognitive load to read through something just to realize that it wasn't necessary in the first place! But I get that this wasn't introduced with this PR, so no worries if you don't get to this right now.
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.
A few minor suggestions (some for a future iteration), but not blocking. Great update!
- You can set tags such as `env:prod` and `app:shopist` on your test. Tags allow you to keep your test suite organized and quickly find tests you're interested in on the homepage. | ||
3. You may create a test using one of the following options: | ||
|
||
- **Create a test from a template**: |
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 a huge deal, but I would consider making these options their own H3 sections in the next iteration.
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.
yeah good callout! We went back and forth on this and landed with this layout for now, but I can improve on this down the road :)
In this example, no specific advanced option is needed. | ||
- Name your test and set tags to it such as `env:prod` and `app:shopist`. Tags allow you to keep your test suite organized and quickly find tests you're interested in on the homepage. | ||
- Choose the browsers and devices you want to test with. | ||
You may create a test using one of the following options: |
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.
You may create a test using one of the following options: | |
You can create a test from a template or from scratch. |
For next time!
- Choose the browsers and devices you want to test with. | ||
You may create a test using one of the following options: | ||
|
||
- **Create a test from a template**: |
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.
- **Create a test from a template**: | |
#### Create a test from a template |
For next time!
Co-authored-by: Rosa Trieu <[email protected]>
/merge |
Devflow running:
|
What does this PR do? What is the motivation?
Adds documentation on Synthetic Monitoring templates for Browser, API test and mobile app testing
Merge instructions
Merge queue is enabled in this repo. To have it automatically merged after it receives the required reviews, create the PR (from a branch that follows the
<yourname>/description
naming convention) and then add the following PR comment:Additional notes