ci: Run SDK browser smoke tests as a separate workflow job #3372
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Separates SDK browser smoke tests from the main browser end-to-end test job into its own dedicated workflow job for better CI visibility and parallel execution.
Changes
npm run test-browser-smokefrom existing browser test jobsdk-browser-smoke-testjob with required Docker services and test environment configuration – this includescassandranow for the resend testing.Note
Separates SDK browser smoke tests from the main browser E2E job and updates test credentials.
sdk-browser-smoke-testjob in.github/workflows/validate.ymlwith browser setup, required Docker services (includingcassandra), and runsnpm run test-browser-smokenpm run test-browser-smokeexecution fromsdk-browser-e2ejobpackages/sdk/test/browser-smoke-test/smoke-test.htmlto use a newPUBLISHER_KEYvalueWritten by Cursor Bugbot for commit 9562af2. This will update automatically on new commits. Configure here.