@testspectra/skills 1.3.1 → 1.3.2

package/dist/skills/network-interception/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: network-interception
-description: The Spectra.intercept() API for deterministic network mocking in TestSpectra — InterceptRule/MockResponse/MockHandle shapes, respondOnce vs respondWith sequential polling, aborting requests, and waitForCall/callCount assertions. Use whenever a test needs to mock, stub, or assert on an API call instead of hitting the real backend.
+description: The Spectra.intercept() API for deterministic network mocking in TestSpectra — InterceptRule/MockResponse/MockHandle shapes, respondOnce vs respondWith sequential polling, aborting requests, and waitForCall/shouldHaveCallCount assertions. Use whenever a test needs to mock, stub, or assert on an API call instead of hitting the real backend.
 ---
 
 # Skill: Network Interception (`Spectra.intercept`)
@@ -31,6 +31,7 @@ interface MockHandle {
   respondOnce(response: MockResponse): this; // one-time FIFO-queued response
   abort(errorCode?: 'Failed' | 'Aborted' | 'TimedOut' | 'ConnectionReset'): this;
   waitForCall(options?: { timeout?: number; count?: number }): Promise<InterceptedRequest>;
+  shouldHaveCallCount(count: number, options?: { timeout?: number }): Promise<void>; // polls; 0 proves no request went out
   readonly callCount: number;
   readonly calls: InterceptedRequest[];
 }
@@ -58,7 +59,7 @@ it('should mock payment failure response gracefully', async () => {
   await CheckoutPage.submitPaymentButton.click();
 
   await paymentMock.waitForCall({ timeout: 5000 });
-  expect(paymentMock.callCount).toBe(1);
+  await paymentMock.shouldHaveCallCount(1);
 
   await CheckoutPage.errorBanner.shouldBeVisible();
   await CheckoutPage.errorBanner.shouldContainText('insufficient funds');
@@ -109,8 +110,9 @@ it('should handle offline mode gracefully when sync fails', async () => {
 - Only mock what the test is actually about — don't blanket-intercept every domain; the linter and
   reviewers expect `monitoredDomains` in `spectra.config.ts` (see the `workspace-structure` skill)
   to reflect real traffic, and over-mocking hides real integration regressions.
-- Always assert on the mock (`waitForCall` / `callCount`) when the test's purpose is to verify the
-  request was made — don't just assert on UI state and silently hope the mock fired.
+- Always assert on the mock (`waitForCall` / `shouldHaveCallCount(n)`) when the test's purpose is to
+  verify the request was made — don't just assert on UI state and silently hope the mock fired. A
+  blocked submit: `shouldHaveCallCount(0)` after the `should*` on the state the app settles in.
 - Every real (non-mocked) network call made during a run is separately captured and written to
   `.testspectra/reports/network-resources.json` for post-run diagnostics — you don't need to record
   this yourself.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@testspectra/skills",
-  "version": "1.3.1",
+  "version": "1.3.2",
   "description": "Installer & manager for modular AI agent skills that standardize TestSpectra script authoring (specs, page objects, steps, actions, hooks, fixtures, matchers)",
   "keywords": [
     "agents",

package/skills/network-interception/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: network-interception
-description: The Spectra.intercept() API for deterministic network mocking in TestSpectra — InterceptRule/MockResponse/MockHandle shapes, respondOnce vs respondWith sequential polling, aborting requests, and waitForCall/callCount assertions. Use whenever a test needs to mock, stub, or assert on an API call instead of hitting the real backend.
+description: The Spectra.intercept() API for deterministic network mocking in TestSpectra — InterceptRule/MockResponse/MockHandle shapes, respondOnce vs respondWith sequential polling, aborting requests, and waitForCall/shouldHaveCallCount assertions. Use whenever a test needs to mock, stub, or assert on an API call instead of hitting the real backend.
 ---
 
 # Skill: Network Interception (`Spectra.intercept`)
@@ -31,6 +31,7 @@ interface MockHandle {
   respondOnce(response: MockResponse): this; // one-time FIFO-queued response
   abort(errorCode?: 'Failed' | 'Aborted' | 'TimedOut' | 'ConnectionReset'): this;
   waitForCall(options?: { timeout?: number; count?: number }): Promise<InterceptedRequest>;
+  shouldHaveCallCount(count: number, options?: { timeout?: number }): Promise<void>; // polls; 0 proves no request went out
   readonly callCount: number;
   readonly calls: InterceptedRequest[];
 }
@@ -58,7 +59,7 @@ it('should mock payment failure response gracefully', async () => {
   await CheckoutPage.submitPaymentButton.click();
 
   await paymentMock.waitForCall({ timeout: 5000 });
-  expect(paymentMock.callCount).toBe(1);
+  await paymentMock.shouldHaveCallCount(1);
 
   await CheckoutPage.errorBanner.shouldBeVisible();
   await CheckoutPage.errorBanner.shouldContainText('insufficient funds');
@@ -109,8 +110,9 @@ it('should handle offline mode gracefully when sync fails', async () => {
 - Only mock what the test is actually about — don't blanket-intercept every domain; the linter and
   reviewers expect `monitoredDomains` in `spectra.config.ts` (see the `workspace-structure` skill)
   to reflect real traffic, and over-mocking hides real integration regressions.
-- Always assert on the mock (`waitForCall` / `callCount`) when the test's purpose is to verify the
-  request was made — don't just assert on UI state and silently hope the mock fired.
+- Always assert on the mock (`waitForCall` / `shouldHaveCallCount(n)`) when the test's purpose is to
+  verify the request was made — don't just assert on UI state and silently hope the mock fired. A
+  blocked submit: `shouldHaveCallCount(0)` after the `should*` on the state the app settles in.
 - Every real (non-mocked) network call made during a run is separately captured and written to
   `.testspectra/reports/network-resources.json` for post-run diagnostics — you don't need to record
   this yourself.