@lunora/testing 1.0.0-alpha.24 → 1.0.0-alpha.241

package/LICENSE.md

@@ -103,3 +103,9 @@ Unless required by applicable law or agreed to in writing, software distributed
 under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR
 CONDITIONS OF ANY KIND, either express or implied. See the License for the
 specific language governing permissions and limitations under the License.
+
+<!-- DEPENDENCIES -->
+<!-- /DEPENDENCIES -->
+
+<!-- TYPE_DEPENDENCIES -->
+<!-- /TYPE_DEPENDENCIES -->

package/README.md

@@ -109,13 +109,19 @@ Each `lunoraTest(...)` opens an in-memory SQLite database; call `t.close()`
 Pass a `fetch` option to replace the throwing stub in action contexts:
 
 ```ts
-const fakeFetch = vi.fn<typeof globalThis.fetch>().mockResolvedValue(Response.json({ ok: true }));
+const fakeFetch = vi.fn<typeof globalThis.fetch>(async () => Response.json({ ok: true }));
 const t = lunoraTest(schema, { fetch: fakeFetch });
 // ctx.fetch inside any action now calls fakeFetch
 ```
 
 Without the option, `ctx.fetch` still throws the v1 error on first access.
 
+#### Injectable `ctx.services`
+
+Pass a `services` option with a fake per `lunora.config` service an action calls
+(`{ documentParser: { fetch } }`). See the [package docs](https://lunora.sh/docs/packages/testing#injectable-ctxservices)
+for an example.
+
 #### Fixed `ctx.now`
 
 Pass a `now` option (epoch ms) to pin `ctx.now` across every context, so
@@ -167,8 +173,14 @@ The virtual clock is **per-harness** — advancing one harness's clock does not
 affect other harnesses, so tests running in parallel are isolated.
 
 Provide a `functions` map (`{ "path:name": registeredFn }`) so the scheduler
-can dispatch jobs. Paths not in the map produce a `console.warn` and are
-silently dropped (matching production behaviour for unknown paths).
+can dispatch jobs. A path not in the map fails the job with `FUNCTION_NOT_FOUND`,
+which then walks the retry budget into `t.scheduler.failures()` — matching
+production, where the DO fires the job at the Worker and dead-letters it.
+
+A retryable failure is re-enqueued silently, so `failures()` only fills once the
+whole backoff schedule (~930s of virtual clock) has elapsed — and at that point
+`advance()`/`runPending()` re-throw the failure by default. Pass
+`{ throwOnError: false }` to inspect `failures()` instead.
 
 #### Subscription testing