Groups n suites #1352
Open
Groups n suites #1352
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
There was a problem hiding this comment.
This screen has already changed @Dgiordano33
There was a problem hiding this comment.
This one looks odd, not connected to the example above?
| @@ -0,0 +1,351 @@ | |||
| --- | |||
| title: Eliminate Alert Fatigue - Organizing Monitoring with Check Suites and Groups | |||
There was a problem hiding this comment.
Suggested change
| title: Eliminate Alert Fatigue - Organizing Monitoring with Check Suites and Groups | |
| title: Eliminate Alert Fatigue - Organize Monitoring with Check Suites and Groups |
| @@ -0,0 +1,351 @@ | |||
| --- | |||
| title: Eliminate Alert Fatigue - Organizing Monitoring with Check Suites and Groups | |||
| displayTitle: Scale Your Monitoring - A Guide to Check Suites and Groups | |||
There was a problem hiding this comment.
Suggested change
| displayTitle: Scale Your Monitoring - A Guide to Check Suites and Groups | |
| displayTitle: Scale Your Monitoring - A Guide to Check Suites and Groups |
💯
| - **When to use**: When tests are interdependent or represent a cohesive user workflow | ||
|
|
||
| ### Check Groups | ||
| [Check Groups](https://www.checklyhq.com/docs/groups/) are **management containers** that organize multiple checks (including Check Suites) for shared configuration and alerting. They focus on **how you manage** your monitoring: |
There was a problem hiding this comment.
Suggested change
| [Check Groups](https://www.checklyhq.com/docs/groups/) are **management containers** that organize multiple checks (including Check Suites) for shared configuration and alerting. They focus on **how you manage** your monitoring: | |
| [Check Groups](https://www.checklyhq.com/docs/groups/) are **folders** that organize multiple checks (including Check Suites) for shared configuration and alerting. They focus on **how you manage** your monitoring: |
| - **Check Suites** = "These tests belong together functionally" | ||
| - **Check Groups** = "These monitors should be managed together operationally" | ||
|
|
||
| A single Check Group can contain multiple Check Suites, and each Check Suite inherits the group's configuration (alerting, scheduling, locations, etc.). |
There was a problem hiding this comment.
Suggested change
| A single Check Group can contain multiple Check Suites, and each Check Suite inherits the group's configuration (alerting, scheduling, locations, etc.). | |
| A single Check Group can contain multiple Check Suites, and each Check Suite optionally inherits the group's configuration (alerting, scheduling, locations, etc.). |
|
|
||
| ### Assigning Playwright Tests to a Check Suite | ||
|
|
||
| Check suites group multiple tests into a single result. Once we’ve imported a test to Checkly, we’ll run these tests as a check suite regularly, and get a report back on the overall results. Here’s an example of the results from a run of a check suite: |
There was a problem hiding this comment.
Suggested change
| Check suites group multiple tests into a single result. Once we’ve imported a test to Checkly, we’ll run these tests as a check suite regularly, and get a report back on the overall results. Here’s an example of the results from a run of a check suite: | |
| Check suites combine multiple tests into a single suite result. Once we’ve imported a test to Checkly, we’ll run these tests as a check suite regularly, and get a report back on the overall results. Here’s an example of the results from a run of a check suite: |
|
|
||
|  | ||
|
|
||
| It makes the most sense to group multiple playwright tests into a Playwright Check Suite when you want to run the tests together, and a failure of any included test would mean that the feature wasn’t working. |
There was a problem hiding this comment.
Suggested change
| It makes the most sense to group multiple playwright tests into a Playwright Check Suite when you want to run the tests together, and a failure of any included test would mean that the feature wasn’t working. | |
| It makes the most sense to group multiple playwright tests into a Playwright Check Suite when you want to run the tests together, and a failure of any included tests would mean that the feature wasn’t working. |
|
|
||
| 1 passed, 1 total | ||
|
|
||
| Tip > Use `--record` to get test results in Checkly with full traces, videos and logs: `npx checkly test --record` |
There was a problem hiding this comment.
I'd rather document TestCommand as an option to ensure they capture / override config options to make this work OR we directly offer a a playwright config example section to copy and paste for traces and videos to be recorded.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Affected Components