qacg/TS-CUCUMBER-WDIO-QK
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Enhance CI configuration and documentation; add new action palette adapter
Some checks failed
CI / validate (push) Has been cancelled
Details

Browse Source
This commit is contained in:
isopropilick
2026-09-15 10:32:11 -06:00
parent 896c3a121a
commit 29899223e4
12 changed files with 296 additions and 11 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
README.md
View File

@@ -1,5 +1,11 @@
# QKForce Framework CWQ
## Generated project execution
Frontend-generated suites use `test/qkforce/manifest.json` (schema 1), exact feature paths, `steps.mjs` and `selectors.json`. The runtime loads only that selection, supplies explicit Cucumber imports and drains legacy palette actions in order. Packaged workspaces without generated inputs fail instead of running template examples. Regenerate projects after migrating to this template revision; publish the runtime to the actual DB-configured Git remote before deploying API #108/frontend #61.
`npm run test:contract` covers config, immutable test data and generated-workspace validation. The separate HTML-report entrypoint gap remains #8. Real browser/client execution remains the release gate.
The QKForce browser-automation template is the fixed `TypeScript + Cucumber + WebdriverIO + QKTestAnalytics` profile.
## Contract status
@@ -68,3 +74,7 @@ npm run check
```
Active development is performed on `develop`.
## Fixed execution and reporting
`npm run qkforce:test` archives the previous cycle, runs WDIO, then builds `qreport-results/index.html` even when WDIO fails. The runner exit code is preserved; report failure makes a successful run fail. No command is accepted from the execution manifest. `qkforce:report` remains available for rebuilding an existing report. Cancellation or a forcibly terminated client cannot guarantee report generation.