♻️ [Test] Added new set of test cases to test JobEngine Device Manage…

…ment Bundle Target Processors Signed-off-by: Alberto Codutti <[email protected]>
eclipse-kapua · Jan 20, 2025 · 23e55f5 · 23e55f5
1 parent 6e39a39
commit 23e55f5
Show file tree

Hide file tree

Showing 3 changed files with 84 additions and 4 deletions.
diff --git a/...test/java/org/eclipse/kapua/integration/service/jobEngine/RunJobEngineServiceI9nTest.java b/...test/java/org/eclipse/kapua/integration/service/jobEngine/RunJobEngineServiceI9nTest.java
@@ -21,7 +21,8 @@
         features = {
 //                "classpath:features/jobEngine/JobEngineServiceOperations.feature",
 //                "classpath:features/jobEngine/JobEngineServiceProcessorKeystoreI9n.feature",
-                "classpath:features/jobEngine/JobEngineServiceProcessorAssetI9n.feature",
+//                "classpath:features/jobEngine/JobEngineServiceProcessorAssetI9n.feature",
+                "classpath:features/jobEngine/JobEngineServiceProcessorBundleI9n.feature",
         },
         glue = {
                 "org.eclipse.kapua.service.job.steps",

diff --git a/...egration/src/test/resources/features/jobEngine/JobEngineServiceProcessorBundleI9n.feature b/...egration/src/test/resources/features/jobEngine/JobEngineServiceProcessorBundleI9n.feature
@@ -0,0 +1,79 @@
+###############################################################################
+# Copyright (c) 2024, 2024 Eurotech and/or its affiliates and others
+#
+# This program and the accompanying materials are made
+# available under the terms of the Eclipse Public License 2.0
+# which is available at https://www.eclipse.org/legal/epl-2.0/
+#
+# SPDX-License-Identifier: EPL-2.0
+#
+# Contributors:
+#     Eurotech - initial API and implementation
+###############################################################################
+@env_docker
+@it
+@jobEngine
+@jobEngineTargetProcessors
+
+Feature: Job Engine Service - Bundle Step Processors
+  Tests for Device Management Bundle Processor
+
+  @setup
+  Scenario: Setup test resources
+    Given Init Security Context
+    And Start Docker environment with resources
+      | db                  |
+      | events-broker       |
+      | job-engine          |
+      | message-broker      |
+      | broker-auth-service |
+      | consumer-lifecycle  |
+
+  Scenario: Bundle Start
+
+    Given I login as user with name "kapua-sys" and password "kapua-password"
+    And I start the Kura Mock
+    And Device birth message is sent
+    And Device "rpione3" is connected within 10s
+    And I create a job with the name "TestJob"
+    And I add device targets to job
+      | rpione3 |
+    And I search for step definition with the name
+      | Bundle Start |
+    And I add job step to job with name "Test Step - Bundle Start" and with selected job step definition and properties
+      | name     | type              | value |
+      | bundleId | java.lang.String  | 34    |
+      | timeout  | java.lang.Long    | 5000  |
+    When I start a job
+    And I wait job to finish its execution up to 10s
+    Then I confirm that job has 1 job execution
+    And I confirm that job target in job has step index 0 and status "PROCESS_OK"
+    # TODO: check that bundle has been started when KuraMock gets refactored
+
+  Scenario: Bundle Stop
+
+    Given I login as user with name "kapua-sys" and password "kapua-password"
+    And I start the Kura Mock
+    And Device birth message is sent
+    And Device "rpione3" is connected within 10s
+    And I create a job with the name "TestJob"
+    And I add device targets to job
+      | rpione3 |
+    And I search for step definition with the name
+      | Bundle Stop |
+    And I add job step to job with name "Test Step - Bundle Stop" and with selected job step definition and properties
+      | name     | type              | value |
+      | bundleId | java.lang.String  | 34    |
+      | timeout  | java.lang.Long    | 5000  |
+    When I start a job
+    And I wait job to finish its execution up to 10s
+    Then I confirm that job has 1 job execution
+    And I confirm that job target in job has step index 0 and status "PROCESS_OK"
+    # TODO: check that bundle has been stopped when KuraMock gets refactored
+
+  @teardown
+  Scenario: Tear down test resources
+    Given I logout
+    And KuraMock is disconnected
+    And Stop Docker environment
+    And Clean Locator Instance
diff --git a/...ration/src/test/resources/features/jobEngine/JobEngineServiceProcessorKeystoreI9n.feature b/...ration/src/test/resources/features/jobEngine/JobEngineServiceProcessorKeystoreI9n.feature
@@ -50,7 +50,7 @@ Feature: Job Engine Service - Keystore Step Processors
     And I wait job to finish its execution up to 10s
     Then I confirm that job has 1 job execution
     And I confirm that job target in job has step index 0 and status "PROCESS_OK"
-    # TODO: check that Item has been installed when KuraMock gets refactored
+    # TODO: check that certificate has been installed when KuraMock gets refactored
 
   Scenario: Keystore Keypair Create Processor
 
@@ -76,7 +76,7 @@ Feature: Job Engine Service - Keystore Step Processors
     And I wait job to finish its execution up to 10s
     Then I confirm that job has 1 job execution
     And I confirm that job target in job has step index 0 and status "PROCESS_OK"
-    # TODO: check that Item has been installed when KuraMock gets refactored
+    # TODO: check that keypair has been created when KuraMock gets refactored
 
   Scenario: Keystore Item Delete Processor
 
@@ -98,7 +98,7 @@ Feature: Job Engine Service - Keystore Step Processors
     And I wait job to finish its execution up to 10s
     Then I confirm that job has 1 job execution
     And I confirm that job target in job has step index 0 and status "PROCESS_OK"
-    # TODO: check that Item has been installed when KuraMock gets refactored
+    # TODO: check that item has been deleted when KuraMock gets refactored
 
   @teardown
   Scenario: Tear down test resources