Deploy preview

https://deploy-preview-23161--material-ui-x.netlify.app/

Bundle size

Details of bundle changes

Check out the code infra dashboard for more information about this PR.

Hey @rita-codes, can you review this pr?

Thanks for working on this! The coverage matches the visibility scope of #23015 and CI is green, but two of the issue's acceptance criteria aren't fully pinned yet:

1. 🟡 The positive assertions don't pin the "renders once" criterion. The acceptance criterion in [scheduler] EventCalendar: multi-resource rendering polish #23015 is that a multi-resource event renders once in each view, and the characteristic failure mode for multi-resource events is duplicate rendering (one occurrence per assigned resource). expect(screen.getAllByText('Team Sync').length).to.be.greaterThan(0) still passes in that case, so the tests can't catch the main regression they're meant to guard against. Since these are timed single-day events (the invisible layout placeholders only apply to all-day events), asserting the exact count is safe here. Applies to the new tests in all four views.
2. 🟡 The color criterion is untested. [scheduler] EventCalendar: multi-resource rendering polish #23015 also lists "color is derived from the first resource" in its scope, but no test in this PR covers it. The behavior is already implemented (schedulerEventSelectors.color resolves through the primary resource id), so it's assertable today — covering it in a single view would be enough, since the selector is shared. Without it, the PR would close the issue with that criterion unpinned.
3. 🟡 Nit: test descriptions in this repo start with "should ..." — the internals tests added in this PR follow the convention, but the new view tests don't. Worth aligning them for consistency.

Thanks for the detailed review! I've addressed all three points:

• Updated the view tests to assert the exact render count so they verify the "renders once" behavior.
• Added a test covering the color criterion using the primary resource.
• Renamed the new view tests to follow the repository's "should ..." naming convention.

The PR has been updated. Could you take another look when you have a chance? Thanks! 🙌

Thank you for the review and the approval! 🙌 I've removed those comments as well. Really appreciate all the feedback throughout this PR!