-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
Consolidate sequential multi-entity-saving tests. #26373
Consolidate sequential multi-entity-saving tests. #26373
Conversation
Size Change: 0 B Total Size: 1.2 MB ℹ️ View Unchanged
|
Link to core editor thread for context https://wordpress.slack.com/archives/C02QB2JS7/p1603273692298300 |
what if we also added |
Interesting. I wonder if that makes sense here? In the example it is used to ensure assertions within passed callbacks actually happen, but here we aren't passing any assertions as callbacks but are just calling the assertions themselves? |
good point! I don't really mind; I've just seen it in a few places and thought it might fit |
9f40f72
to
1cc35c1
Compare
Description
Discussions in core slack with @talldan and @youknowriad pointed out sequential tests can be problematic. This PR consolidates multi-entity-saving tests that are dependent on each others steps into the same test blocks.
How has this been tested?
Screenshots
Types of changes
Checklist: