playwright-order-manager 0.1.2 → 0.1.3

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.
Files changed (2) hide show
  1. package/README.md +18 -0
  2. package/package.json +1 -1
package/README.md CHANGED
@@ -110,6 +110,24 @@ That's it. The runner will:
110
110
 
111
111
  ---
112
112
 
113
+ ## Reference Demo Project
114
+
115
+ A full reference consumer project is available at pw-order-demo, including fixture usage, ordered execution, reports, verification workflow, and programmatic usage examples.
116
+
117
+ For a full working consumer example, see the [`pw-order-demo`](https://github.com/rajeshyemul/pw-order-demo) reference project.
118
+
119
+ That repo shows how to use `playwright-order-manager` in a real Playwright project, including:
120
+
121
+ - importing `test` from `playwright-order-manager/fixtures`
122
+ - tagging tests with `@runFirst`, `@runLast`, `@P1`, `@P2`, and `@P3`
123
+ - running ordered execution with `pw-order`
124
+ - generating and opening ordered reports
125
+ - verifying mixed-priority tests in the same file
126
+ - using `TestOrderManager.run(...)` programmatically from a custom Node script
127
+
128
+ If you want installation and package-level documentation, use this repository.
129
+ If you want a practical end-to-end consumer example, use `pw-order-demo`.
130
+
113
131
  ## Execution Order
114
132
 
115
133
  Given tests tagged with various priorities, the execution order is always:
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "playwright-order-manager",
3
- "version": "0.1.2",
3
+ "version": "0.1.3",
4
4
  "description": "Priority-ordered test execution for Playwright",
5
5
  "main": "./dist/index.js",
6
6
  "types": "./dist/index.d.ts",