Skip to content

fix(storefront): consume the expected_status override per request #56

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
roncodes merged 1 commit into from
Aug 31, 2026
Merged

fix(storefront): consume the expected_status override per request #56

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions postman/collections/Fleetbase Storefront API/.resources/definition.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -19,7 +19,12 @@ scripts:
// must answer 402) opts out of the 2xx expectation by setting `expected_status`
// in its beforeRequest script. The error-payload check is skipped for it too —
// the error body is exactly what such a request is asserting.
//
// The override is consumed here, immediately after being read. "Local" variables
// are scoped to the RUN, not the request — left set, one request's 402 override
// held every later request in the run against [402], failing ten healthy 200s.
const expectedOverride = Number(pm.variables.get('expected_status')) || null;
pm.variables.unset('expected_status');
const expected = expectedOverride
? [expectedOverride]
: (pm.request.method === 'POST' ? [200, 201, 202] : [200, 201, 202, 204]);
Expand Down
Loading