38 lines
1.5 KiB
Markdown
38 lines
1.5 KiB
Markdown
# Changelog
|
|
|
|
All notable changes to QKForce Framework CWQ are recorded here.
|
|
|
|
## Unreleased
|
|
|
|
No unreleased changes.
|
|
|
|
## 0.2.0 - 2026-09-11
|
|
|
|
### Review fixes
|
|
|
|
- Regenerate the lockfile from the registry for QKTestAnalytics 0.4.1.
|
|
- Build portable HTML through the fixed test entrypoint after runner success or failure and preserve nonzero status.
|
|
- Add entrypoint failure/report sequencing tests and verify HTML presence in CI.
|
|
|
|
|
|
Initial release candidate for the fixed QKForce execution template.
|
|
|
|
### Added
|
|
|
|
- Fixed TypeScript, Cucumber, WebdriverIO and QKTestAnalytics execution profile.
|
|
- Generated-project manifest validation and deterministic `qkforce:test` entrypoint.
|
|
- Canonical `features/`, `steps/` and page-object layout shared with the FrontEnd generator.
|
|
- QKTestAnalytics adapter integration, result manifests and portable template contract documentation.
|
|
- Dependency-free structural tests for generated project paths and execution entrypoints.
|
|
|
|
### Changed
|
|
|
|
- QKForce-generated suites use `test/qkforce/manifest.json` as the runtime provenance boundary.
|
|
- The template consumes `@qacg/qk-test-analytics` 0.4.1 at the manifest level.
|
|
|
|
### Known limitations
|
|
|
|
- The Analytics 0.4.1 lockfile is regenerated and clean-install/contract checks pass; merge and exact-candidate CI evidence remain required (#10).
|
|
- A successful required terminal CI run on the release candidate is still needed (#6).
|
|
- Portable report orchestration is implemented; passing/failing real-scenario acceptance remains tracked in #8.
|