You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix(testing-sdk): reject waitForData promises when execution completes (#318)
*Issue #, if available:*
#317
*Description of changes:*
Preventing hanging promises if execution completes while waitForData is
pending. Before, waitForData would never resolve/reject when the
execution completes and the operation was not found. Now, it will reject
all of the pending promises when it completes.
By submitting this pull request, I confirm that you can use, modify,
copy, and redistribute this contribution, under the terms of your
choice.
Copy file name to clipboardExpand all lines: packages/aws-durable-execution-sdk-js-testing/src/test-runner/cloud/__tests__/cloud-durable-test-runner.test.ts
"Operation was not found after execution completion. Expected status: STARTED. This typically means the operation was never executed or the test is waiting for the wrong operation.",
884
+
),
885
+
);
886
+
});
887
+
888
+
it("should reject pending operation promises when execution fails",async()=>{
"Operation was not found after execution completion. Expected status: STARTED. This typically means the operation was never executed or the test is waiting for the wrong operation.",
"Operation was not found after execution completion. Expected status: COMPLETED. This typically means the operation was never executed or the test is waiting for the wrong operation.",
Copy file name to clipboardExpand all lines: packages/aws-durable-execution-sdk-js-testing/src/test-runner/local/__tests__/integration/local-durable-test-runner.integration.test.ts
"Operation was not found after execution completion. Expected status: STARTED. This typically means the operation was never executed or the test is waiting for the wrong operation.",
0 commit comments