Skip to content

Scheduler - Unskip testcafe tests#33200

Merged
Tucchhaa merged 3 commits intoDevExpress:26_1from
Tucchhaa:unskip_tests_26_1
Apr 9, 2026
Merged

Scheduler - Unskip testcafe tests#33200
Tucchhaa merged 3 commits intoDevExpress:26_1from
Tucchhaa:unskip_tests_26_1

Conversation

@Tucchhaa
Copy link
Copy Markdown
Contributor

@Tucchhaa Tucchhaa commented Apr 8, 2026

No description provided.

].forEach(({ views, expect, crossScrollingEnabled }) => {
views.forEach((view) => {
test.skip(
test(
Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looking at the history:
https://github.com/Tucchhaa/DevExtreme/blame/b7f2e313133634034b38ecba8b20f81a76fed120/e2e/testcafe-devextreme/tests/scheduler/common/layout/customization/cellSizesCss.ts#L98

This test was skipped from the moment it was added, looks like it was an accident, so I just unskipped it

currentDate: new Date(2020, 8, 7),
scrolling: {
mode: 'virtual',
orientation: 'both',
Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Private option, I removed it, because the default value is also 'both':

const DefaultScrollingOrientation = scrollingOrientations.both;

scrolling: {
mode: 'virtual',
orientation: 'both',
outlineCount: 0,
Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Private option. This option determines how many rows or columns to render outside the viewport if virtual scrolling is enabled. It's redundant in the case of this test, because appointment is always in the viewport (on init and after scroll)

const scheduler = new Scheduler('#container');
const { element } = scheduler.getAppointment('', 0);

await setStyleAttribute(element, 'background-color: red;');
Copy link
Copy Markdown
Contributor Author

@Tucchhaa Tucchhaa Apr 9, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This background-color is set here just to check if the value of the style attr hasn't changed (if appt is rerendered then style attr value will reset)

@Tucchhaa Tucchhaa marked this pull request as ready for review April 9, 2026 04:02
@Tucchhaa Tucchhaa requested a review from a team as a code owner April 9, 2026 04:02
Copilot AI review requested due to automatic review settings April 9, 2026 04:02
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR re-enables previously skipped Scheduler TestCafe coverage by unskipping two tests and adjusting one test’s expectations/config so it can run in CI.

Changes:

  • Unskipped the virtual scrolling “appointment should not repaint after scrolling” test and updated it to compare against the captured initial inline style.
  • Removed scrolling.orientation and scrolling.outlineCount from the virtual scrolling scheduler setup.
  • Unskipped the “cell sizes CSS classes” layout customization test matrix.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

File Description
e2e/testcafe-devextreme/tests/scheduler/common/virtualScrolling/appointments.ts Unskips a virtual scrolling test, relaxes the style assertion by capturing the initial style, and removes extra scrolling options.
e2e/testcafe-devextreme/tests/scheduler/common/layout/customization/cellSizesCss.ts Unskips the cell size/CSS class verification tests across views and cross-scrolling modes.

aleksei-semikozov
aleksei-semikozov approved these changes Apr 9, 2026
@Tucchhaa Tucchhaa merged commit 287a173 into DevExpress:26_1 Apr 9, 2026
387 of 389 checks passed
@Tucchhaa Tucchhaa deleted the unskip_tests_26_1 branch April 9, 2026 15:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants