test: pass limit query param in limit-only unpaginated test

TheLastCicada · TheLastCicada · commit b951fe614010 · 2026-04-23T13:47:26.000-07:00
The test claimed to verify that a bare `?limit=10` request (no `page`)
is handled as unpaginated, but the body sent no query parameters at
all, making it indistinguishable from the earlier "no query params"
test. Bugbot flagged that a future regression where `isPaginated`
also triggered on `limit` would slip past this guard. Send the
intended query parameter so the test verifies its namesake.
diff --git a/tests/resources/staging.spec.js b/tests/resources/staging.spec.js
@@ -184,10 +184,14 @@ describe('Staging Resource CRUD', function () {
         .stub(Staging, 'getDiffObjects')
         .resolves([{ original: { warehouseUnitId: 'unit-1' }, change: {} }]);
 
-      const response = await supertest(app).get('/v1/staging').expect(200);
+      const response = await supertest(app)
+        .get('/v1/staging')
+        .query({ limit: 10 })
+        .expect(200);
 
       expect(findAllStub.calledOnce).to.be.true;
       expect(findAndCountAllStub.called).to.be.false;
+      expect(getDiffObjectsStub.calledOnce).to.be.true;
       expect(findAllStub.firstCall.args[0]).to.deep.equal({
         where: {},
         order: [['id', 'ASC']],
