Skip to content
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.

Sign up for GitHub

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

Jump to bottom

InputEvent_RespondsOnKeystrokes test failure #27397

Closed
BrennanConroy opened this issue Oct 30, 2020 · 2 comments
Closed

InputEvent_RespondsOnKeystrokes test failure #27397

BrennanConroy opened this issue Oct 30, 2020 · 2 comments
Assignees
@pranavkm
Labels
area-blazor Includes: Blazor, Razor Components test-failure

Comments

@BrennanConroy
Copy link
Member 

Microsoft.AspNetCore.Components.E2ETest.Tests.EventTest.InputEvent_RespondsOnKeystrokes [FAIL]
      OpenQA.Selenium.BrowserAssertFailedException : Xunit.Sdk.NotEmptyException: Assert.NotEmpty() Failure
         at Xunit.Assert.NotEmpty(IEnumerable collection) in C:\Dev\xunit\xunit\src\xunit.assert\Asserts\CollectionAsserts.cs:line 331
         at Microsoft.AspNetCore.E2ETesting.WaitAssert.<>c__DisplayClass15_0.<Exists>b__0() in /_/src/Shared/E2ETesting/WaitAssert.cs:line 72
         at Microsoft.AspNetCore.E2ETesting.WaitAssert.<>c__DisplayClass18_0`1.<WaitAssertCore>b__0(IWebDriver _) in /_/src/Shared/E2ETesting/WaitAssert.cs:line 109
      Screen shot captured at 'F:\workspace\_work\1\s\artifacts\TestResults\Release\Microsoft.AspNetCore.Components.E2ETests\3685e73c9df9487a99364936cb6df36f.png'
      Page content:
      <head>
          <meta charset="utf-8">
          <title>Basic test app</title>
          <base href="/subdir/">
          <link href="style.css" rel="stylesheet">
          <link rel="icon" href="data:,">
      
          <!-- Used by ExternalContentPackage -->
          <link href="_content/TestContentPackage/styles.css" rel="stylesheet">
      
          <!-- App bundle that contains a reference to the scoped css bundle created by TestContentPackage -->
          <link href="BasicTestApp.styles.css" rel="stylesheet">
      </head>
      
      <body>
          <root>Loading...</root>
      
          <!-- Explicit display:none required so StartupErrorNotificationTest can observe it change -->
          <div id="blazor-error-ui" style="display: none;">
              An unhandled error has occurred.
              <a href="" class="reload">Reload</a>
              <a class="dismiss" style="cursor: pointer;">??</a>
          </div>
      
          <!-- Used for specific test cases -->
          <script src="js/seleniumworkaround.js"></script>
          <script src="js/jsinteroptests.js"></script>
          <script src="js/renderattributestest.js"></script>
          <script src="js/webComponentPerformingJsInterop.js"></script>
      
          <script>
              // Used by ElementRefComponent
              function setElementValue(element, newValue) {
                  element.value = newValue;
                  return element.value;
              }
      
              function navigationManagerNavigate() {
                  Blazor.navigateTo('/subdir/some-path');
              }
      
              function getCurrentUrl() {
                  return location.href;
              }
          </script>
          <script src="_framework/blazor.webassembly.js"></script>
      
          <script src="_content/Microsoft.AspNetCore.Components.Web.Extensions/headManager.js"></script>
      
          <!-- Used by ExternalContentPackage -->
          <script src="_content/TestContentPackage/prompt.js"></script>
      
      
      
      <script type="text/javascript">var Module; window.__wasmmodulecallback__(); delete window.__wasmmodulecallback__;</script><script src="_framework/dotnet.6.0.0-alpha.1.20468.7.js" defer="" integrity="sha256-VXwIh6nczBDI+UPb+gdp64GkUP5qSz86FUs8Xhsc92E=" crossorigin="anonymous"></script></body>
      
      ---- Assert.NotEmpty() Failure
      Stack Trace:
        /_/src/Shared/E2ETesting/WaitAssert.cs(139,0): at Microsoft.AspNetCore.E2ETesting.WaitAssert.WaitAssertCore[TResult](IWebDriver driver, Func`1 assertion, TimeSpan timeout)
        /_/src/Shared/E2ETesting/WaitAssert.cs(67,0): at Microsoft.AspNetCore.E2ETesting.WaitAssert.Exists(IWebDriver driver, By finder, TimeSpan timeout)
        /_/src/Components/test/E2ETest/Infrastructure/WebDriverExtensions/BasicTestAppWebDriverExtensions.cs(24,0): at Microsoft.AspNetCore.Components.E2ETest.BasicTestAppWebDriverExtensions.WaitUntilTestSelectorReady(IWebDriver browser)
        /_/src/Components/test/E2ETest/Infrastructure/WebDriverExtensions/BasicTestAppWebDriverExtensions.cs(18,0): at Microsoft.AspNetCore.Components.E2ETest.BasicTestAppWebDriverExtensions.MountTestComponent[TComponent](IWebDriver browser)
        /_/src/Components/test/E2ETest/Tests/EventTest.cs(29,0): at Microsoft.AspNetCore.Components.E2ETest.Tests.EventTest.InitializeAsyncCore()
        /_/src/Shared/E2ETesting/BrowserTestBase.cs(71,0): at Microsoft.AspNetCore.E2ETesting.BrowserTestBase.InitializeAsync(String isolationContext)
        ----- Inner Stack Trace -----
        /_/src/Shared/E2ETesting/WaitAssert.cs(72,0): at Microsoft.AspNetCore.E2ETesting.WaitAssert.<>c__DisplayClass15_0.<Exists>b__0()
        /_/src/Shared/E2ETesting/WaitAssert.cs(109,0): at Microsoft.AspNetCore.E2ETesting.WaitAssert.<>c__DisplayClass18_0`1.<WaitAssertCore>b__0(IWebDriver _)
@BrennanConroy BrennanConroy added test-failure area-blazor Includes: Blazor, Razor Components labels Oct 30, 2020
@mkArtakMSFT mkArtakMSFT added this to the 6.0-preview1 milestone Nov 2, 2020
@ghost
Copy link

ghost commented Apr 22, 2021

Thanks for contacting us.
We're moving this issue to the Next sprint planning milestone for future evaluation / consideration. Because it's not immediately obvious that this is a bug in our framework, we would like to keep this around to collect more feedback, which can later help us determine the impact of it. We will re-evaluate this issue, during our next planning meeting(s).
If we later determine, that the issue has no community involvement, or it's very rare and low-impact issue, we will close it - so that the team can focus on more important and high impact issues.
To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.

@pranavkm
Copy link
Contributor

pranavkm commented Jun 4, 2021

Closing in favor of #31195.

@pranavkm pranavkm closed this as completed Jun 4, 2021
@pranavkm pranavkm removed this from the 6.0-preview6 milestone Jun 4, 2021
@ghost ghost locked as resolved and limited conversation to collaborators Jul 4, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@pranavkm pranavkm

Labels
area-blazor Includes: Blazor, Razor Components test-failure
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@pranavkm @BrennanConroy @mkArtakMSFT