@activate-core/test-forge 2.4.1 → 2.4.2
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 +6 -4
- package/dist/core/generate/harness.js +9 -5
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -459,10 +459,12 @@ file, outside any test. `--no-scan` skips the look-up.
|
|
|
459
459
|
`run` stops that area before running anything and prints the `npm i -D` to
|
|
460
460
|
run, instead of every test failing as if the product were broken. A test that
|
|
461
461
|
still hits it is reported as skipped with that reason. The same goes for the
|
|
462
|
-
testkit's sign-in check: it uses an endpoint no journey tests, and when
|
|
463
|
-
|
|
464
|
-
|
|
465
|
-
|
|
462
|
+
testkit's sign-in check: it uses an endpoint no journey tests, and when that
|
|
463
|
+
endpoint answers with anything but a 200 the testkit signs in afresh once and
|
|
464
|
+
carries on, so one broken endpoint never stops the suite. A run signs each role
|
|
465
|
+
in once, not once per test file. A testkit built before this that still stops on
|
|
466
|
+
the check has its failures reported as not started, with the status and the
|
|
467
|
+
endpoint, not as failing their rules. `run` also says when
|
|
466
468
|
`TESTFORGE_KEY` is set but `dashboardUrl` is empty, so a run that will not be
|
|
467
469
|
published is not a surprise.
|
|
468
470
|
|
|
@@ -108,11 +108,15 @@ export const HARNESS_CONTRACT = [
|
|
|
108
108
|
` - That check uses the lightest authenticated endpoint the role can call,`,
|
|
109
109
|
` one that only says who is signed in, never a screen's data endpoint that`,
|
|
110
110
|
` a journey tests: a bug there would stop every test before it starts.`,
|
|
111
|
-
` - Only
|
|
112
|
-
`
|
|
113
|
-
`
|
|
114
|
-
`
|
|
115
|
-
`
|
|
111
|
+
` - Only a 200 confirms a token. Any other answer (a refusal, a 5xx from a bug`,
|
|
112
|
+
` or a local database behind the schema, a 429) leaves it unconfirmed: mint`,
|
|
113
|
+
` a fresh one once through the real login and use it, so one broken endpoint`,
|
|
114
|
+
` never stops every test. Never retry the check per test.`,
|
|
115
|
+
` - Each test file loads the testkit anew: a token minted by another file of`,
|
|
116
|
+
` the run in the last few minutes (cached with the time it was minted) is`,
|
|
117
|
+
` used as it is, so a run logs each role in once, not once per file.`,
|
|
118
|
+
` - When the login itself fails, throw "testkit: login as <identifier> failed`,
|
|
119
|
+
` (<status>)": that, not the check, is what stops the role's tests.`,
|
|
116
120
|
` - Check connections by their live state and reopen them if closed; do not`,
|
|
117
121
|
` use "already set up" flags. Tests never disconnect the shared connection.`,
|
|
118
122
|
`H5. Nothing destructive outside test data.`,
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@activate-core/test-forge",
|
|
3
|
-
"version": "2.4.
|
|
3
|
+
"version": "2.4.2",
|
|
4
4
|
"description": "AI-powered QA automation. Scans a project, drafts journey docs, and generates seeded Jest/Playwright tests. Works in any project, with any AI CLI.",
|
|
5
5
|
"type": "module",
|
|
6
6
|
"bin": {
|