Skip to content

Add declarative response assertions and a controlled payload Runner #3

Closed

Description

@user-github-me

User problem

API testing needs repeatable expectations and a controlled way to try boundary values.

Acceptance criteria

  • Check HTTP status, header presence/equality/content, JSON Pointer values, response text, time, and byte budgets.
  • Save assertions with Builder, Repeater, and collection requests.
  • Run assertions for every payload and display passed/failed counts plus per-result details.
  • Run at most 50 payloads sequentially against one origin, with delays, timeouts and cancellation.
  • Provide numeric, JSON type and string boundary presets, CSV results, replay and comparison.
  • Fail assertions on network errors and clean temporary request rules after cancellation.

Implementation status

Implemented and verified in PR #1 on feat/v1.1-workbench. PR #1 was merged into main on 2026-10-03, merge commit eeb65009fa6e343cf6dd1f67386be0afc5bbb3e5. GitHub automatically closed this issue as completed through the PR's closing reference. The source changes are now on main; the Chrome Web Store release remains pending.

Verification

Node tests exercise assertion success/failure, JSON Pointer and network errors. Brave integration exercises Runner ordering, cancellation/timeouts, rule cleanup and Builder assertions.

Relevant source

lab.js, lab-ui.js, workflow-ui.js, dashboard.js, tests/lab.test.js

Related v1.1 work is tracked through PR #1. Follow-up improvements or bugs should use their own issue and PR.

Completion record

The implementation commits are 7b76001, 3ee1668, 4f1d89c, 504051e, and test follow-up 619736d. Relevant verification is described above and in PR #1. All 29 Node regressions and JavaScript syntax checks pass; GitHub CI passes on Node 22. The workbench/browser features were checked with isolated local HTTP/WebSocket fixtures; shortcut labels were also checked for Mac/Windows/Linux platforms. The maintainer merged PR #1, and GitHub closed this issue automatically; new bugs or follow-up scope should use a separate issue, or reopen this one if its original criteria fail.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions