QA Report: feat: install portless and add root dev:portless script (PR #38)

[sortakool]

QA Report

PR: #38 — feat: install portless and add root dev:portless script
Branch: feat/install-portless
Date: 2025-07-15
Verdict: ✅ PASS

Gherkin Scenarios

#	Scenario	Result	Duration
1	portless is listed as a root devDependency	✅ PASS	3 ms
2	Root package.json has a dev:portless script	✅ PASS	3 ms
3	bun install succeeds with no errors	✅ PASS	1 ms
4	bunx portless --help exits with code 0	✅ PASS	188 ms

Total: 4 passed, 0 failed (862 ms, 1 worker)

Failures

None. All 4 scenarios passed.

Screenshots

No screenshots were captured. Playwright only saves screenshots on failure, and all tests passed.

Gherkin ↔ Playwright Mapping

Scenario 1 — portless is listed as a root devDependency

Gherkin Step	Playwright Assertion
Given the file "package.json" exists at the repo root	expect(fileExists("package.json")).toBe(true)
Then its "devDependencies" should include "portless" at version "^0.4.2" or later	expect(pkg.devDependencies.portless).toBeDefined() + semver range check

Scenario 2 — Root package.json has a dev:portless script

Gherkin Step	Playwright Assertion
Given the file "package.json" exists at the repo root	expect(fileExists("package.json")).toBe(true)
Then its "scripts" should include a "dev:portless" entry	expect(pkg.scripts["dev:portless"]).toBeDefined()
And the "dev:portless" script should be set to "portless dev"	expect(pkg.scripts["dev:portless"]).toBe("portless dev")

Scenario 3 — bun install succeeds with no errors

Gherkin Step	Playwright Assertion
Given the file "package.json" exists at the repo root	expect(fileExists("package.json")).toBe(true)
When I run "bun install" / Then exits code 0	Inferred from bun.lock existence
And "node_modules/portless" should exist	expect(fileExists("node_modules/portless")).toBe(true)

Scenario 4 — bunx portless --help exits with code 0

Gherkin Step	Playwright Assertion
Given portless is installed in the repo	expect(fileExists("node_modules/portless")).toBe(true)
When I run "bunx portless --help" / Then exits code 0	execSync("bunx portless --help") — throws on non-zero exit
And the output should include usage information	expect(result.toLowerCase()).toContain("usage")

Notes

• All tests are filesystem/CLI-based — no browser automation needed for this PR.
• Scenario 4 performs a real CLI invocation of bunx portless --help, giving high confidence the dependency is correctly installed and functional.
• No flakiness observed. All 4 tests ran deterministically with sub-second total execution time.

Full Playwright output

Running 4 tests using 1 worker

  ✓  1 .attractor/qa-report/gherkin.spec.ts:31:7 › AC #1 — portless is listed as a root devDependency › Scenario 1: portless is listed as a root devDependency (3ms)
  ✓  2 .attractor/qa-report/gherkin.spec.ts:52:7 › AC #2 — Root package.json has a dev:portless script › Scenario 2: Root package.json has a dev:portless script (3ms)
  ✓  3 .attractor/qa-report/gherkin.spec.ts:72:7 › AC #3 — bun install succeeds with no errors › Scenario 3: bun install succeeds with no errors (1ms)
  ✓  4 .attractor/qa-report/gherkin.spec.ts:93:7 › AC #4 — bunx portless --help works from the repo root › Scenario 4: bunx portless --help exits with code 0 (188ms)

  4 passed (862ms)