Flaky test: InputDateInteractsWithEditContext_NullableDateTimeOffset

[rokonec]

Failing test

Microsoft.AspNetCore.Components.E2ETest.Tests.FormsInputDateTest.InputDateInteractsWithEditContext_NullableDateTimeOffset

Summary

The FormsInputDateTest family of WebAssembly E2E tests is intermittently failing again in the aspnetcore-components-e2e pipeline. These tests drive native date/time <input> elements via Selenium SendKeys, and have a long history of keyboard-input timing flakiness (see #27398, #31734, #34884, #35018). The failures present as the EditContext reporting modified invalid instead of modified valid when keystrokes are dropped/reordered.

InputDateInteractsWithEditContext_NullableDateTimeOffset shares the same root cause and is being re-quarantined alongside its sibling tests on the servicing branches.

Observed CI failure (sibling test in the same class)

Pipeline: aspnetcore-components-e2e

OpenQA.Selenium.BrowserAssertFailedException : Xunit.Sdk.EqualException: Assert.Equal() Failure
Expected: modified valid
Actual:   modified invalid
   at Xunit.Assert.Equal[T](T expected, T actual, IEqualityComparer`1 comparer)
   at Microsoft.AspNetCore.E2ETesting.WaitAssert.<>c__DisplayClass18_0`1.<WaitAssertCore>b__0(IWebDriver _) in /home/vsts/work/1/s/src/Shared/E2ETesting/WaitAssert.cs:line 101

(The captured failure above is for InputDateInteractsWithEditContext_NonNullableDateTime, tracked in #31734. NullableDateTimeOffset exercises the same SendKeys-driven flow and is being quarantined as part of the same group.)

Action

Re-quarantining on the servicing branches so the cookie-auth security backports are not blocked by unrelated flakiness:

• release/8.0 — [release/8.0] Reject ASCII control characters in cookie auth return URLs #67157
• release/9.0 — [release/9.0] Reject ASCII control characters in cookie auth return URLs #67156

[github-actions]

Triage Summary

Area: area-blazor (Blazor WebAssembly E2E test in Microsoft.AspNetCore.Components.E2ETest.Tests.FormsInputDateTest)
Type: Bug (intermittently failing CI test — EditContext reports modified invalid instead of modified valid due to SendKeys keystroke timing flakiness in native date/time <input> elements)

Potential Duplicates

• InputDateInteractsWithEditContext_NonNullableDateTime test flakiness #31734 - InputDateInteractsWithEditContext_NonNullableDateTime test flakiness (similarity: high — same FormsInputDateTest class, same root cause, identical error message)
• Quarantining InputDateInteractsWithEditContext_TimeInput #35018 - Quarantining InputDateInteractsWithEditContext_TimeInput (similarity: high — same FormsInputDateTest Selenium timing flakiness pattern, same quarantine action)

Generated by Triage Comment Reviewer for dotnet/aspnetcore for issue #67243 · 43.5 AIC · ⌖ 37.9 AIC · ⊞ 24.9K · ◷

[oroztocil]

@rokonec How do you want to proceed with the quarantining? I see that you added the attribute in the backport PRs but not in the main PR.

[Youssef1313]

@ilonatommy Should this be closed now that #68125 and #68126 are merged?