Merge remote-tracking branch 'origin/dev' into issue/OSOE-402

Lombiq.Tests.UI.Samples/Tests/BasicVisualVerificationTests.cs

@@ -55,7 +55,8 @@ public Task VerifyBlogImage() =>
     // is the different rendering of text on each platform, but it can occur between different Linux distributions too.
     // Here: https://pandasauce.org/post/linux-fonts/ you can find a good summary about this from 2019, but still valid
     // in 2022.
-    [Theory, Chrome, Edge]
+    // Temporarily not running Edge until https://github.com/atata-framework/atata-webdriversetup/issues/16 is fixed.
+    [Theory, Chrome]
     public Task VerifyNavbar(Browser browser) =>
         ExecuteTestAfterSetupAsync(
             context =>

Lombiq.Tests.UI.Samples/Tests/MultiBrowserTests.cs

@@ -23,15 +23,18 @@ public MultiBrowserTests(ITestOutputHelper testOutputHelper)
 
     // First, let's see a test using Edge. While the default browser is Chrome if you don't set anything, all
     // ExecuteTest* methods can also accept a browser, if you want to use a different one.
-    [Fact]
+#pragma warning disable xUnit1004 // Test methods should not be skipped
+    [Fact(Skip = "Temporarily not running Edge until https://github.com/atata-framework/atata-webdriversetup/issues/16 is fixed.")]
+#pragma warning restore xUnit1004 // Test methods should not be skipped
     public Task AnonymousHomePageShouldExistWithEdge() =>
         ExecuteTestAfterSetupAsync(NavbarIsCorrect, Browser.Edge);
 
     // This test is now marked not with the [Fact] attribute but [Theory]. With it, you can create so-called data-driven
     // tests. [Chrome] and [Edge] are input parameters of the test, and thus in effect, you have now two tests:
     // AnonymousHomePageShouldExistMultiBrowser once with Chrome, and once with Edge. See here for more info:
     // https://andrewlock.net/creating-parameterised-tests-in-xunit-with-inlinedata-classdata-and-memberdata/.
-    [Theory, Chrome, Edge]
+    // Temporarily not running Edge until https://github.com/atata-framework/atata-webdriversetup/issues/16 is fixed.
+    [Theory, Chrome]
     public Task AnonymousHomePageShouldExistMultiBrowser(Browser browser) =>
         ExecuteTestAfterSetupAsync(NavbarIsCorrect, browser);