@testream/playwright-reporter 1.2.3 → 1.2.4
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +33 -4
- package/package.json +12 -6
package/README.md
CHANGED
|
@@ -1,8 +1,17 @@
|
|
|
1
|
-
# @testream/playwright-reporter
|
|
1
|
+
# @testream/playwright-reporter: Playwright test reporting for Jira
|
|
2
2
|
|
|
3
|
-
|
|
3
|
+
`@testream/playwright-reporter` publishes Playwright test results from CI/CD to Testream, where they become durable test evidence that teams can inspect from Jira. Playwright remains the execution source: Testream does not require you to recreate every automated test as a manual Jira case.
|
|
4
4
|
|
|
5
|
-
##
|
|
5
|
+
## What the reporter sends to Testream and Jira
|
|
6
|
+
|
|
7
|
+
- Passed, failed, skipped, and flaky Playwright results
|
|
8
|
+
- Failure messages, stack traces, traces, screenshots, and videos
|
|
9
|
+
- Branch, commit, build, environment, and CI context
|
|
10
|
+
- Suite changes and historical trends for release and Jira visibility
|
|
11
|
+
|
|
12
|
+
This gives engineering, QA, and product teams a shared view of current automated evidence without replacing the Playwright suite or CI pipeline they already use.
|
|
13
|
+
|
|
14
|
+
## Install and configure
|
|
6
15
|
|
|
7
16
|
```bash
|
|
8
17
|
npm install --save-dev @testream/playwright-reporter
|
|
@@ -22,4 +31,24 @@ export default defineConfig({
|
|
|
22
31
|
});
|
|
23
32
|
```
|
|
24
33
|
|
|
25
|
-
|
|
34
|
+
Store `TESTREAM_API_KEY` as a protected CI secret. The reporter runs with Playwright and publishes structured evidence after the test run, so the same setup works in GitHub Actions, GitLab CI/CD, Azure Pipelines, Jenkins, and other command-based CI systems.
|
|
35
|
+
|
|
36
|
+
## Playwright evidence in CI/CD
|
|
37
|
+
|
|
38
|
+
Keep running Playwright normally. Testream connects its results and artifacts to the relevant project, Jira work, and release context. Teams can inspect failures, compare suite changes, and follow quality trends while traces and browser evidence remain tied to the run that produced them.
|
|
39
|
+
|
|
40
|
+
## Frequently asked questions
|
|
41
|
+
|
|
42
|
+
### Do we need to recreate automated tests as manual Jira cases?
|
|
43
|
+
|
|
44
|
+
No. Your code-first Playwright suite remains the source of execution. Testream publishes its results as Jira-visible evidence without requiring a parallel manual test case for every automated test.
|
|
45
|
+
|
|
46
|
+
### Does this work with Playwright projects and CI retries?
|
|
47
|
+
|
|
48
|
+
Yes. The reporter captures Playwright’s structured results across configured projects and preserves retry and failure context in the published run.
|
|
49
|
+
|
|
50
|
+
## Official Testream resources
|
|
51
|
+
|
|
52
|
+
- [Playwright Jira integration](https://testream.app/playwright-jira-integration)
|
|
53
|
+
- [Complete Playwright reporter setup guide](https://docs.testream.app/reporters/playwright)
|
|
54
|
+
- [Install Testream – Automated Test Management for Jira](https://marketplace.atlassian.com/3048460704)
|
package/package.json
CHANGED
|
@@ -1,7 +1,8 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@testream/playwright-reporter",
|
|
3
|
-
"version": "1.2.
|
|
4
|
-
"description": "Playwright
|
|
3
|
+
"version": "1.2.4",
|
|
4
|
+
"description": "Publish Playwright test results, traces, screenshots, videos, and CI metadata to Testream and Jira.",
|
|
5
|
+
"homepage": "https://testream.app/playwright-jira-integration",
|
|
5
6
|
"main": "dist/index.js",
|
|
6
7
|
"types": "dist/index.d.ts",
|
|
7
8
|
"scripts": {
|
|
@@ -19,12 +20,17 @@
|
|
|
19
20
|
"url": "git+https://github.com/testream/docs.git"
|
|
20
21
|
},
|
|
21
22
|
"keywords": [
|
|
23
|
+
"testream",
|
|
22
24
|
"playwright",
|
|
23
|
-
"reporter",
|
|
24
|
-
"
|
|
25
|
+
"playwright-reporter",
|
|
26
|
+
"playwright-jira",
|
|
27
|
+
"jira",
|
|
25
28
|
"test-management",
|
|
26
|
-
"test-
|
|
27
|
-
"
|
|
29
|
+
"automated-test-management",
|
|
30
|
+
"test-reporting",
|
|
31
|
+
"ci-cd",
|
|
32
|
+
"ctrf",
|
|
33
|
+
"e2e"
|
|
28
34
|
],
|
|
29
35
|
"author": "Testream",
|
|
30
36
|
"license": "SEE LICENSE IN LICENSE",
|