Skip unit tests for Release that are colliding with each other while we investigate how to address their flaky behavior

Author: normj

Tools/LambdaTestTool-v2/tests/Amazon.Lambda.TestTool.UnitTests/Commands/RunCommandTests.cs

@@ -21,7 +21,11 @@ public class RunCommandTests
     private readonly Mock<IToolInteractiveService> _mockInteractiveService = new Mock<IToolInteractiveService>();
     private readonly Mock<IRemainingArguments> _mockRemainingArgs = new Mock<IRemainingArguments>();
 
+#if DEBUG
     [Fact]
+#else
+    [Fact(Skip = "Skipping this test as it is not working properly.")]
+#endif
     public async Task ExecuteAsync_LambdaRuntimeApi_SuccessfulLaunch()
     {
         // Arrange
@@ -45,7 +49,11 @@ public async Task ExecuteAsync_LambdaRuntimeApi_SuccessfulLaunch()
         Assert.True(isApiRunning);
     }
 
+#if DEBUG
     [Fact]
+#else
+    [Fact(Skip = "Skipping this test as it is not working properly.")]
+#endif
     public async Task ExecuteAsync_ApiGatewayEmulator_SuccessfulLaunch()
     {
         // Arrange
@@ -70,7 +78,11 @@ public async Task ExecuteAsync_ApiGatewayEmulator_SuccessfulLaunch()
         Assert.True(isApiRunning);
     }
 
+#if DEBUG
     [Fact]
+#else
+    [Fact(Skip = "Skipping this test as it is not working properly.")]
+#endif
     public async Task ExecuteAsync_EnvPorts_SuccessfulLaunch()
     {
         var lambdaPort = TestHelpers.GetNextLambdaRuntimePort();

Tools/LambdaTestTool-v2/tests/Amazon.Lambda.TestTool.UnitTests/RuntimeApiTests.cs

@@ -18,7 +18,11 @@ namespace Amazon.Lambda.TestTool.UnitTests;
 
 public class RuntimeApiTests
 {
+#if DEBUG
     [Fact]
+#else
+    [Fact(Skip = "Skipping this test as it is not working properly.")]
+#endif
     public async Task AddEventToDataStore()
     {
         const string functionName = "FunctionFoo";
@@ -71,7 +75,11 @@ public async Task AddEventToDataStore()
         }
     }
 
+#if DEBUG
     [Fact]
+#else
+    [Fact(Skip = "Skipping this test as it is not working properly.")]
+#endif
     public async Task InvokeRequestResponse()
     {
         const string functionName = "FunctionFoo";