Skip to content

Refactor test#33004

Open
Raushen wants to merge 3 commits intoDevExpress:26_1from
Raushen:Fix-unstable-6
Open

Refactor test#33004
Raushen wants to merge 3 commits intoDevExpress:26_1from
Raushen:Fix-unstable-6

Conversation

@Raushen
Copy link
Contributor

@Raushen Raushen commented Mar 20, 2026

No description provided.

@Raushen Raushen self-assigned this Mar 20, 2026
@Raushen Raushen requested a review from a team as a code owner March 20, 2026 21:19
Copilot AI review requested due to automatic review settings March 20, 2026 21:19
@Raushen Raushen added the 26_1 label Mar 20, 2026
Copy link
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

Refactors the DataGrid sticky columns + grouping screenshot coverage (TestCafe) by splitting the previous “horizontal scroll” scenario into two separate screenshot tests and adjusting the widget configuration used to reproduce the overlap/intersection cases.

Changes:

  • Removed the unstable meta flag and the runtime apiOption('summary.totalItems', ...) mutation + repeated scroll/waits from the existing test.
  • Introduced a second dedicated test case for the “total summary” scenario and adjusted customizeColumns/summary configuration for both cases.
  • Renamed the original test title to explicitly call out the “intersection” scenario.

@@ -291,31 +291,15 @@ test('DataGrid - Group row content is scrolled if repaintChangesOnly is enabled
// T1284612
test.meta({
browserSize: [900, 800],
Copy link
Contributor

Choose a reason for hiding this comment

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

Check, please, whether we need custom browserSize for these test.
We set width and height for DataGrid in its configuration, then make screenshot of the grid only, looks like custom window size not used

customizeColumns(columns) {
columns[2].groupIndex = 0;
columns[1].visible = false;
columns[4].width = 150;
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggestion: return back previous logic with changing grid option in runtime to change summary.totalItelm and column[index].width. This will save us time on initial page render

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I do not agree. It is difficult to create one config for 4 cases. Also I do not think initial render takes a lot of time.

Copilot AI review requested due to automatic review settings March 23, 2026 10:05
Copy link
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

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

totalItems: [{
column: 'SaleAmount',
summaryType: 'max',
valueFormat: 'currency',
Copy link

Copilot AI Mar 23, 2026

Choose a reason for hiding this comment

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

The total summary displayFormat string MAXMAXMAXMAX: {0} is hard to interpret and looks like a placeholder. If the intent is to force a long label for layout coverage, consider using a clearer long label (or add a brief inline comment explaining why this specific text is needed) to keep the test configuration self-explanatory.

Suggested change
valueFormat: 'currency',
valueFormat: 'currency',
// Use a deliberately long caption to verify layout/width handling of total summary text.

Copilot uses AI. Check for mistakes.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants