From 028ee44a24019b70743722ba01e4b36bce8ec6ab Mon Sep 17 00:00:00 2001 From: Saranya Date: Thu, 2 Nov 2023 12:14:20 -0700 Subject: [PATCH] Revert "feat: confidence test case template (#40)" (#41) This reverts commit c6849418a59a4f865e37e6645ffa6a8246a8f638. --- .../features/confidenceTest.feature | 53 ------------------- 1 file changed, 53 deletions(-) delete mode 100644 templates/java/TestTemplateForCLI/src/main/resources/greengrass/features/confidenceTest.feature diff --git a/templates/java/TestTemplateForCLI/src/main/resources/greengrass/features/confidenceTest.feature b/templates/java/TestTemplateForCLI/src/main/resources/greengrass/features/confidenceTest.feature deleted file mode 100644 index 27f6b8d..0000000 --- a/templates/java/TestTemplateForCLI/src/main/resources/greengrass/features/confidenceTest.feature +++ /dev/null @@ -1,53 +0,0 @@ -Feature: Confidence Test suite - - Background: - Given my device is registered as a Thing - And my device is running Greengrass - - @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 - | 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 restart Greengrass - Then I wait 5 seconds - # 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 GDK_COMPONENT_NAME component is RUNNING using the greengrass-cli \ No newline at end of file