Skip to content
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.

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

✅ Unique ID per test in submit tests #663

Merged
merged 1 commit into from
Jun 11, 2024
Merged

✅ Unique ID per test in submit tests #663

merged 1 commit into from
Jun 11, 2024

Conversation

alecgibson
Copy link
Collaborator

@alecgibson alecgibson commented May 29, 2024

We've had some issues with state from one test bleeding into another.

This happens because all of our submit.js tests use the same collection and ID.

This change makes them instead use sequential IDs for each test, which should give each test better isolation from other tests.

@coveralls
Copy link

coveralls commented May 29, 2024

Coverage Status

coverage: 97.445%. remained the same
when pulling 2138407 on submit-id
into 3cdecf4 on master.

@alecgibson alecgibson force-pushed the submit-id branch 3 times, most recently from d171c79 to 70ec2df Compare June 11, 2024 16:27
We've had some issues with state from one test bleeding into another.

This happens because all of our `submit.js` tests use the same
collection and ID.

This change makes them instead use sequential IDs for each test, which
should give each test better isolation from other tests.
@alecgibson alecgibson merged commit 89b8237 into master Jun 11, 2024
7 checks passed
@alecgibson alecgibson deleted the submit-id branch June 11, 2024 16:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants