-
Notifications
You must be signed in to change notification settings - Fork 9
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/test list #48
Feat/test list #48
Conversation
Suite foldedTest Suite Summary5 passed, 3 failed, and 3 skipped/pending/other
|
With PR Comment - Run #70
❌ Some tests failed!
|
With PR Comment No Fails - Run #70
🎉 All tests passed! |
With PR Comment On Fail Only With Fails - Run #70
❌ Some tests failed!
|
Create a Custom Summary!You can effortlessly generate custom test summaries and PR comments using your CTRF report, Handlebars and Markdown. Example: Generating a SummaryLet's start with the basics, a summary table that gives an overview of your test ctrf (you might have seen this one somewhere!). This table is straightforward yet powerful, helping you quickly communicate the state of your tests:
This table is generated by referencing various properties from your CTRF report, making it easy to create detailed and customized summaries. In addition, you can leverage custom methods like Count of flaky tests: 3 Remember, you're not just writing markdown—you're writing markdown enhanced with Handlebars, which means you can take full advantage of markdown's features while adding dynamic content. Example: Iterating Over the Tests ArrayNext, let's focus on generating a report specifically for failed tests. To do this, we'll iterate through the CTRF tests array and filter out the failed tests:
Locator: locator(':root') You might have noticed, this one is using a helper called HTMLIf raw markdown isn't quite working for you, GitHub also renders some HTML. Here is the same failed table in HTML:
Notice the use of the stripAnsi method, as some error messages contain ANSI. Adding Extra Markdown ElementsYou can further enrich your summaries by tagging collaborators, adding tasks, and linking to important resources. Here's how: Tag a collaborator:You might want to notify someone specific, like @Ma11hewThomas. You can add tasks!
Include useful links:Adding Collapsible SectionsIf you have extensive details that might clutter your summary, you can use collapsible sections to hide and reveal information as needed: See detailed test results
Locator: locator(':root')
GitHub propertiesThere are various GitHub properties you can tap into!
|
Pull Request Arg
Failed Tests
Flaky Tests
Detailed Test Results
|
Suite foldedTest Suite Summary5 passed, 3 failed, and 3 skipped/pending/other
|
With PR Comment - Run #72
❌ Some tests failed!
|
With PR Comment No Fails - Run #72
🎉 All tests passed! |
With PR Comment On Fail Only With Fails - Run #72
❌ Some tests failed!
|
Create a Custom Summary!You can effortlessly generate custom test summaries and PR comments using your CTRF report, Handlebars and Markdown. Example: Generating a SummaryLet's start with the basics, a summary table that gives an overview of your test ctrf (you might have seen this one somewhere!). This table is straightforward yet powerful, helping you quickly communicate the state of your tests:
This table is generated by referencing various properties from your CTRF report, making it easy to create detailed and customized summaries. In addition, you can leverage custom methods like Count of flaky tests: 3 Remember, you're not just writing markdown—you're writing markdown enhanced with Handlebars, which means you can take full advantage of markdown's features while adding dynamic content. Example: Iterating Over the Tests ArrayNext, let's focus on generating a report specifically for failed tests. To do this, we'll iterate through the CTRF tests array and filter out the failed tests:
Locator: locator(':root') You might have noticed, this one is using a helper called HTMLIf raw markdown isn't quite working for you, GitHub also renders some HTML. Here is the same failed table in HTML:
Notice the use of the stripAnsi method, as some error messages contain ANSI. Adding Extra Markdown ElementsYou can further enrich your summaries by tagging collaborators, adding tasks, and linking to important resources. Here's how: Tag a collaborator:You might want to notify someone specific, like @Ma11hewThomas. You can add tasks!
Include useful links:Adding Collapsible SectionsIf you have extensive details that might clutter your summary, you can use collapsible sections to hide and reveal information as needed: See detailed test results
Locator: locator(':root')
GitHub propertiesThere are various GitHub properties you can tap into!
|
Pull Request Arg
Failed Tests
Flaky Tests
Detailed Test Results
|
No description provided.