@kody-ade/kody-engine-lite 0.1.126 → 0.1.127
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/package.json +2 -1
- package/skills/playwright-cli.md +63 -0
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@kody-ade/kody-engine-lite",
|
|
3
|
-
"version": "0.1.
|
|
3
|
+
"version": "0.1.127",
|
|
4
4
|
"description": "Autonomous SDLC pipeline: Kody orchestration + Claude Code + LiteLLM",
|
|
5
5
|
"license": "MIT",
|
|
6
6
|
"type": "module",
|
|
@@ -10,6 +10,7 @@
|
|
|
10
10
|
"files": [
|
|
11
11
|
"dist",
|
|
12
12
|
"prompts",
|
|
13
|
+
"skills",
|
|
13
14
|
"templates",
|
|
14
15
|
"kody.config.schema.json"
|
|
15
16
|
],
|
|
@@ -0,0 +1,63 @@
|
|
|
1
|
+
# Playwright CLI
|
|
2
|
+
|
|
3
|
+
You have Playwright CLI installed and available. Use it for running E2E and integration tests.
|
|
4
|
+
|
|
5
|
+
## When to Use
|
|
6
|
+
|
|
7
|
+
- Run the full test suite to verify changes don't break existing functionality
|
|
8
|
+
- Run specific tests related to the files you modified
|
|
9
|
+
- Debug test failures by re-running with verbose output
|
|
10
|
+
|
|
11
|
+
## Running Tests
|
|
12
|
+
|
|
13
|
+
```bash
|
|
14
|
+
# Run all tests
|
|
15
|
+
npx playwright test
|
|
16
|
+
|
|
17
|
+
# Run specific test file
|
|
18
|
+
npx playwright test tests/e2e/login.spec.ts
|
|
19
|
+
|
|
20
|
+
# Run tests matching a pattern
|
|
21
|
+
npx playwright test --grep "checkout"
|
|
22
|
+
|
|
23
|
+
# Run in a specific browser
|
|
24
|
+
npx playwright test --project=chromium
|
|
25
|
+
|
|
26
|
+
# Run with verbose output for debugging
|
|
27
|
+
npx playwright test --reporter=list
|
|
28
|
+
|
|
29
|
+
# Run a single test by title
|
|
30
|
+
npx playwright test -g "should display error message"
|
|
31
|
+
```
|
|
32
|
+
|
|
33
|
+
## Reading Failures
|
|
34
|
+
|
|
35
|
+
When tests fail, Playwright outputs:
|
|
36
|
+
- **Test name** and file location
|
|
37
|
+
- **Expected vs received** values for assertions
|
|
38
|
+
- **Call log** showing what Playwright did before failure
|
|
39
|
+
- **Screenshot/trace paths** if configured
|
|
40
|
+
|
|
41
|
+
Focus on the assertion diff first — it usually tells you exactly what's wrong.
|
|
42
|
+
|
|
43
|
+
## Debugging
|
|
44
|
+
|
|
45
|
+
```bash
|
|
46
|
+
# Show detailed trace on failure
|
|
47
|
+
npx playwright test --trace on
|
|
48
|
+
|
|
49
|
+
# Run headed (visible browser) for debugging
|
|
50
|
+
npx playwright test --headed
|
|
51
|
+
|
|
52
|
+
# Run in debug mode with inspector
|
|
53
|
+
npx playwright test --debug
|
|
54
|
+
|
|
55
|
+
# Retry failed tests
|
|
56
|
+
npx playwright test --retries=1
|
|
57
|
+
```
|
|
58
|
+
|
|
59
|
+
## Common Patterns
|
|
60
|
+
|
|
61
|
+
- If a test fails due to timing, check for missing `await` or add `expect().toBeVisible()` waits
|
|
62
|
+
- If selectors break, use `getByRole()`, `getByText()`, or `getByTestId()` — they're more stable than CSS selectors
|
|
63
|
+
- After fixing code, re-run only the failing test first before running the full suite
|