<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Integration Testing on a Blazor Front End in Integration and Testing</title>
    <link>https://community.developer.cybersource.com/t5/Integration-and-Testing/Integration-Testing-on-a-Blazor-Front-End/m-p/83658#M52766</link>
    <description>&lt;P class=""&gt;What are people using for integration testing for a Blazor app?&lt;/P&gt;&lt;P class=""&gt;I wanted to do the testing with Playwright, but I'm more of a JS guy, so jumping straight into Playwright in C# proved a bit difficult for me. I decided to just go with Selenium in C# using xUnit, as that's what the devs are using for unit tests.&lt;/P&gt;&lt;P class=""&gt;I've been writing tests in an xunit Selenium framework and I am getting killed by stale element errors. There are times when I have a wait until an element is visible, followed by a wait for element to be clickable, then finally the click method, only to get a stale element error. I even tried to set up a retry method, but it only retries if the assertion fails, not if an exception is thrown at some other point in the test.&lt;/P&gt;&lt;P class=""&gt;Is this a problem inherent to Blazor apps or are we just doing something wrong here?&lt;/P&gt;</description>
    <pubDate>Fri, 05 Aug 2022 11:51:24 GMT</pubDate>
    <dc:creator>AkinBredailik</dc:creator>
    <dc:date>2022-08-05T11:51:24Z</dc:date>
    <item>
      <title>Integration Testing on a Blazor Front End</title>
      <link>https://community.developer.cybersource.com/t5/Integration-and-Testing/Integration-Testing-on-a-Blazor-Front-End/m-p/83658#M52766</link>
      <description>&lt;P class=""&gt;What are people using for integration testing for a Blazor app?&lt;/P&gt;&lt;P class=""&gt;I wanted to do the testing with Playwright, but I'm more of a JS guy, so jumping straight into Playwright in C# proved a bit difficult for me. I decided to just go with Selenium in C# using xUnit, as that's what the devs are using for unit tests.&lt;/P&gt;&lt;P class=""&gt;I've been writing tests in an xunit Selenium framework and I am getting killed by stale element errors. There are times when I have a wait until an element is visible, followed by a wait for element to be clickable, then finally the click method, only to get a stale element error. I even tried to set up a retry method, but it only retries if the assertion fails, not if an exception is thrown at some other point in the test.&lt;/P&gt;&lt;P class=""&gt;Is this a problem inherent to Blazor apps or are we just doing something wrong here?&lt;/P&gt;</description>
      <pubDate>Fri, 05 Aug 2022 11:51:24 GMT</pubDate>
      <guid>https://community.developer.cybersource.com/t5/Integration-and-Testing/Integration-Testing-on-a-Blazor-Front-End/m-p/83658#M52766</guid>
      <dc:creator>AkinBredailik</dc:creator>
      <dc:date>2022-08-05T11:51:24Z</dc:date>
    </item>
  </channel>
</rss>

