Closed Ma11hewThomas closed 2 months ago
Tests π | Passed β | Failed β | Skipped βοΈ | Pending β³ | Other β | Flaky π | Duration β±οΈ |
---|---|---|---|---|---|---|---|
10 | 10 | 0 | 0 | 0 | 0 | 0 | 00:00:11 |
Tests π | Passed β | Failed β | Skipped βοΈ | Pending β³ | Other β | Flaky π | Duration β±οΈ |
---|---|---|---|---|---|---|---|
10 | 5 | 3 | 1 | 1 | 1 | 3 | 00:00:11 |
Name | Status | Failure Message |
---|---|---|
should display title | failed β | Timed out 5000ms waiting for expect(locator).toHaveTitle(expected) Locator: locator(':root') Expected pattern: /Playwrc cight/ Received string: "Fast and reliable end-to-end testing for modern web apps | Playwright" Call log: - expect.toHaveTitle with timeout 5000ms - waiting for locator(':root') - locator resolved to β¦ - unexpected value "Fast and reliable end-to-end testing for modern web apps | Playwright" |
should fail to update profile on network failure | failed β | Network Timeout |
should fail to update profile on network failure | failed β | No failure message |
You can effortlessly generate custom test summaries and PR comments using your CTRF report, Handlebars and Markdown.
Let'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:
Tests π | Passed β | Failed β | Skipped βοΈ | Pending β³ | Other β | Flaky π | Duration β±οΈ |
---|---|---|---|---|---|---|---|
10 | 5 | 3 | 1 | 1 | 1 | 3 | 00:00:11 |
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 countFlaky
and formatDuration
to enhance your summary:
Count of flaky tests: 3 Duration of execution: 00:00:11
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.
Next, 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:
Name | Status | Failure Message |
---|---|---|
should display title | failed β | [31mTimed out 5000ms waiting for [39m[2mexpect([22m[31mlocator[39m[2m).[22mtoHaveTitle[2m([22m[32mexpected[39m[2m)[22m |
Locator: locator(':root') Expected pattern: [32m/Playwrc cight/[39m Received string: [31m"Fast and reliable end-to-end testing for modern web apps | Playwright"[39m Call log: [2m- expect.toHaveTitle with timeout 5000ms[22m [2m - waiting for locator(':root')[22m [2m - locator resolved to <html lang="en" dir="ltr" data-theme="light" data-has-β¦>β¦</html>[22m [2m - unexpected value "Fast and reliable end-to-end testing for modern web apps | Playwright"[22m |
---|---|---|
should fail to update profile on network failure | failed β | Network Timeout |
should fail to update profile on network failure | failed β | No failure message |
You might have noticed, this one is using a helper called eq
. You can use this for property comparisons directly within your template logic.
If raw markdown isn't quite working for you, GitHub also renders some HTML.
Here is the same failed table in HTML:
Name | Status | Failure Message |
---|---|---|
should display title | failed β | Timed out 5000ms waiting for expect(locator).toHaveTitle(expected) Locator: locator(':root') Expected pattern: /Playwrc cight/ Received string: "Fast and reliable end-to-end testing for modern web apps | Playwright" Call log: - expect.toHaveTitle with timeout 5000ms - waiting for locator(':root') - locator resolved to <html lang="en" dir="ltr" data-theme="light" data-has-β¦>β¦</html> - unexpected value "Fast and reliable end-to-end testing for modern web apps | Playwright" |
should fail to update profile on network failure | failed β | Network Timeout |
should fail to update profile on network failure | failed β | No failure message |
Notice the use of the stripAnsi method, as some error messages contain ANSI.
You can further enrich your summaries by tagging collaborators, adding tasks, and linking to important resources. Here's how:
You might want to notify someone specific, like @Ma11hewThomas.
If you have extensive details that might clutter your summary, you can use collapsible sections to hide and reveal information as needed:
There are various GitHub properties you can tap into!
With PR Comment - Run #539
β Some tests failed!
Github Actions Test Reporter CTRF