@vasanth-mv/pqs-cli 1.1.0

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 ADDED
@@ -0,0 +1,126 @@
1
+ # pqs — Code Quality Studio CLI
2
+
3
+ Audit your test files from the terminal. Supports every stack the UI supports:
4
+ Playwright, Cypress, Selenium, Appium, TOSCA, REST Assured, Postman, and more.
5
+
6
+ ---
7
+
8
+ ## Install
9
+
10
+ ### One-time setup (from the repo)
11
+
12
+ ```bash
13
+ cd playwright-quality-studio/cli
14
+ npm install # installs esbuild
15
+ npm run build # bundles everything → dist/pqs.js
16
+ npm install -g . # registers the `pqs` command globally
17
+ ```
18
+
19
+ ### Upgrade
20
+
21
+ ```bash
22
+ cd playwright-quality-studio/cli
23
+ npm run build
24
+ npm install -g .
25
+ ```
26
+
27
+ ---
28
+
29
+ ## Usage
30
+
31
+ ```
32
+ pqs [path...] [options]
33
+ ```
34
+
35
+ | Option | Description |
36
+ |---|---|
37
+ | `-s, --stack <id>` | Force a stack (default: auto-detected) |
38
+ | `-S, --severity <level>` | Filter: `all` · `critical` · `warning` · `info` |
39
+ | `-c, --category <id>` | Filter by category id |
40
+ | `-o, --output <fmt>` | `pretty` (default) · `json` · `summary` |
41
+ | `--no-color` | Disable ANSI colours |
42
+ | `--list-stacks` | Print all stack IDs and exit |
43
+ | `-h, --help` | Show help |
44
+
45
+ ---
46
+
47
+ ## Examples
48
+
49
+ ```bash
50
+ # Analyse current folder (auto-detects stack)
51
+ pqs .
52
+
53
+ # Analyse a specific folder with a forced stack
54
+ pqs ./tests/ --stack cypress
55
+
56
+ # Show only critical findings
57
+ pqs ./e2e/ --severity critical
58
+
59
+ # Pipe JSON to a file for CI artefacts
60
+ pqs ./tests/ --output json > report.json
61
+
62
+ # Summary line (great for CI logs)
63
+ pqs ./tests/ --output summary
64
+
65
+ # Filter by category
66
+ pqs ./tests/ --category reliability
67
+
68
+ # Multiple paths
69
+ pqs ./src/tests/ ./e2e/ --stack playwright
70
+ ```
71
+
72
+ ---
73
+
74
+ ## Available stacks
75
+
76
+ Run `pqs --list-stacks` to see all IDs. Quick reference:
77
+
78
+ | ID | Stack |
79
+ |---|---|
80
+ | `playwright` | Playwright TS/JS |
81
+ | `playwright_java` | Playwright Java |
82
+ | `playwright_python` | Playwright Python |
83
+ | `cypress` | Cypress TS/JS |
84
+ | `selenium_java` | Selenium Java |
85
+ | `selenium_csharp` | Selenium C# |
86
+ | `appium_java` | Appium Java |
87
+ | `tosca_xml` | TOSCA XML export |
88
+ | `restassured` | REST Assured |
89
+ | `karate` | Karate |
90
+ | `pytest_api` | pytest (API) |
91
+ | `postman` | Postman JSON |
92
+ | `java_api` | Java API |
93
+ | `typescript` | TypeScript |
94
+ | `python_api` | Python API |
95
+
96
+ ---
97
+
98
+ ## CI integration
99
+
100
+ `pqs` exits with code `1` when critical findings are found — plug it straight into
101
+ your pipeline:
102
+
103
+ ```yaml
104
+ # GitHub Actions example
105
+ - name: Audit test quality
106
+ run: pqs ./tests/ --output summary
107
+ # fails the step if any critical finding exists
108
+ ```
109
+
110
+ ```bash
111
+ # Pre-commit hook (~/.git/hooks/pre-commit)
112
+ pqs . --severity critical --output summary || exit 1
113
+ ```
114
+
115
+ ---
116
+
117
+ ## Output formats
118
+
119
+ ### `pretty` (default)
120
+ Coloured terminal output — file list, per-finding details, category score bars.
121
+
122
+ ### `json`
123
+ Machine-readable — `{ stack, files, avgScore, summary, results[] }`.
124
+
125
+ ### `summary`
126
+ One-line status: `pqs ⚡ Playwright TS/JS · 12 files · score 74 · 2 critical · 5 warning`