@izkac/forgekit 0.3.4 → 0.3.5
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
CHANGED
|
@@ -87,11 +87,17 @@ a loop is complex exactly when the feature has many wiring seams, which is
|
|
|
87
87
|
when wiring silently breaks. Never skip the loop for complexity; control its
|
|
88
88
|
cost instead:
|
|
89
89
|
|
|
90
|
-
- **Ask before building
|
|
91
|
-
|
|
92
|
-
|
|
93
|
-
|
|
94
|
-
|
|
90
|
+
- **Ask before building complex harness infrastructure — and only then.**
|
|
91
|
+
The ask-line is infrastructure: a rig built from scratch, new
|
|
92
|
+
servers/containers/services, third-party accounts or sandboxes (e.g. real
|
|
93
|
+
payment checkout), device farms. That is a project, not a test — stop and
|
|
94
|
+
ask the user. **Everything below that line never needs permission**: if a
|
|
95
|
+
harness already exists (test server, isolated ports, scratch DB), author
|
|
96
|
+
the loop; writing fixtures, seed data, helper scripts, or extra steps
|
|
97
|
+
inside the existing rig is normal test work — just do it. Asking for
|
|
98
|
+
fixture-level work is over-asking; skipping the loop because the rig is
|
|
99
|
+
missing is under-testing — the ask is exactly the moment the operator can
|
|
100
|
+
say "build it once" and make every future loop on the project cheap.
|
|
95
101
|
- **One executed loop per capability, not per assertion.** Push edge cases
|
|
96
102
|
into unit tests; e2e proves the wiring exists.
|
|
97
103
|
- **Set `timeoutMs` from the step count up front.** A 10-step loop is never a
|