feat: complete confidence test suite with additional four tests (#43)

aws-greengrass · Nov 15, 2023 · bbca2f1 · bbca2f1
1 parent ed8a048
commit bbca2f1
Showing 1 changed file with 62 additions and 2 deletions.
diff --git a/...tes/java/TestTemplateForCLI/src/main/resources/greengrass/features/confidenceTest.feature b/...tes/java/TestTemplateForCLI/src/main/resources/greengrass/features/confidenceTest.feature
@@ -14,6 +14,22 @@ Feature: Confidence Test Suite
     # Update component state accordingly. Possible states: {RUNNING, FINISHED, BROKEN, STOPPING}
     And I verify the GDK_COMPONENT_NAME component is RUNNING using the greengrass-cli
 
+  @ConfidenceTest
+  Scenario: As a Developer, I can deploy GDK_COMPONENT_NAME, stop it and start it again
+    When I create a Greengrass deployment with components
+      | GDK_COMPONENT_NAME | GDK_COMPONENT_RECIPE_FILE |
+      | aws.greengrass.Cli | LATEST                    |
+    And I deploy the Greengrass deployment configuration
+    Then the Greengrass deployment is COMPLETED on the device after 180 seconds
+    # Update component state accordingly. Possible states: {RUNNING, FINISHED, BROKEN, STOPPING}
+    Then I verify the GDK_COMPONENT_NAME component is RUNNING using the greengrass-cli
+    When I use greengrass-cli to stop the component GDK_COMPONENT_NAME
+    # Update component state accordingly. Possible states: {RUNNING, FINISHED, BROKEN, STOPPING}
+    Then I verify the GDK_COMPONENT_NAME component is FINISHED using the greengrass-cli
+    When I use greengrass-cli to restart the component GDK_COMPONENT_NAME
+    # Update component state accordingly. Possible states: {RUNNING, FINISHED, BROKEN, STOPPING}
+    Then I verify the GDK_COMPONENT_NAME component is RUNNING using the greengrass-cli
+
   @ConfidenceTest
   Scenario: As a Developer, I can deploy GDK_COMPONENT_NAME and restart Greengrass to check if it is still working as expected
     When I create a Greengrass deployment with components
@@ -28,6 +44,24 @@ Feature: Confidence Test Suite
     # Update component state accordingly. Possible states: {RUNNING, FINISHED, BROKEN, STOPPING}
     And I verify the GDK_COMPONENT_NAME component is RUNNING using the greengrass-cli
 
+  @ConfidenceTest
+  Scenario: As a Developer, I can deploy GDK_COMPONENT_NAME and disable internet to check if component is working. Restore internet to check if component is still working
+    When I create a Greengrass deployment with components
+      | GDK_COMPONENT_NAME | GDK_COMPONENT_RECIPE_FILE |
+      | aws.greengrass.Cli | LATEST                    |
+    And I deploy the Greengrass deployment configuration
+    Then the Greengrass deployment is COMPLETED on the device after 180 seconds
+    # Update component state accordingly. Possible states: {RUNNING, FINISHED, BROKEN, STOPPING}
+    Then I verify the GDK_COMPONENT_NAME component is RUNNING using the greengrass-cli
+    When I set device network connectivity to OFFLINE
+    And I restart Greengrass
+    Then I wait 5 seconds
+    # Update component state accordingly. Possible states: {RUNNING, FINISHED, BROKEN, STOPPING}
+    Then I verify the GDK_COMPONENT_NAME component is RUNNING using the greengrass-cli
+    When I set device network connectivity to ONLINE
+    # Update component state accordingly. Possible states: {RUNNING, FINISHED, BROKEN, STOPPING}
+    Then I verify the GDK_COMPONENT_NAME component is RUNNING using the greengrass-cli
+
   @ConfidenceTest
   Scenario: As a Developer, I can deploy GDK_COMPONENT_NAME to my device and see it is working as expected after an additional local deployment to change component configuration
     When I create a Greengrass deployment with components
@@ -46,8 +80,9 @@ Feature: Confidence Test Suite
           }
         }
       """
+    Then the local Greengrass deployment is SUCCEEDED on the device after 120 seconds
     # Update component state accordingly. Possible states: {RUNNING, FINISHED, BROKEN, STOPPING}. Additional verification steps may be added here too.
-    Then I verify the GDK_COMPONENT_NAME component is RUNNING using the greengrass-cli
+    And I verify the GDK_COMPONENT_NAME component is RUNNING using the greengrass-cli
 
   @ConfidenceTest
   Scenario: As a Developer, I can deploy GDK_COMPONENT_NAME to my device with configuration updates and see it is working as expected
@@ -67,4 +102,29 @@ Feature: Confidence Test Suite
     Then the Greengrass deployment is COMPLETED on the device after 180 seconds
     # Update component state accordingly. Possible states: {RUNNING, FINISHED, BROKEN, STOPPING}. Additional verification steps may be added here too.
     Then I verify the GDK_COMPONENT_NAME component is RUNNING using the greengrass-cli
-
+
+  @ConfidenceTest
+  Scenario: As a Developer, I can deploy GDK_COMPONENT_NAME to my device and verify device RAM has not increased by more than a specified threshold
+    When I record the device's RAM usage statistic as RAM1
+    And I create a Greengrass deployment with components
+      | GDK_COMPONENT_NAME | GDK_COMPONENT_RECIPE_FILE |
+      | aws.greengrass.Cli | LATEST                    |
+    And I deploy the Greengrass deployment configuration
+    Then the Greengrass deployment is COMPLETED on the device after 180 seconds
+  # Update component state accordingly. Possible states: {RUNNING, FINISHED, BROKEN, STOPPING}
+    Then I verify the GDK_COMPONENT_NAME component is RUNNING using the greengrass-cli
+    When I record the device's RAM usage statistic as RAM2
+    Then the increase in the RAM usage from RAM1 to RAM2 is less than 1024 MB
+
+  @ConfidenceTest
+  Scenario: As a Developer, I can deploy GDK_COMPONENT_NAME to my device and verify device CPU usage has not increased by more than a specified threshold
+    When I record the device's CPU usage statistic as CPU1
+    And I create a Greengrass deployment with components
+      | GDK_COMPONENT_NAME | GDK_COMPONENT_RECIPE_FILE |
+      | aws.greengrass.Cli | LATEST                    |
+    And I deploy the Greengrass deployment configuration
+    Then the Greengrass deployment is COMPLETED on the device after 180 seconds
+  # Update component state accordingly. Possible states: {RUNNING, FINISHED, BROKEN, STOPPING}
+    Then I verify the GDK_COMPONENT_NAME component is RUNNING using the greengrass-cli
+    When I record the device's CPU usage statistic as CPU2
+    Then the increase in the CPU usage from CPU1 to CPU2 is less than 25 percent