♻️ [Test] Removed TODO. Checking of DeviceEvents and effectivness of …

…the Device Management operation will be tested by the Device Management tests Signed-off-by: Alberto Codutti <[email protected]>
eclipse-kapua · Jan 20, 2025 · f5378fb · f5378fb
1 parent 3bb84f8
commit f5378fb
Show file tree

Hide file tree

Showing 5 changed files with 0 additions and 10 deletions.
diff --git a/...tegration/src/test/resources/features/jobEngine/JobEngineServiceProcessorAssetI9n.feature b/...tegration/src/test/resources/features/jobEngine/JobEngineServiceProcessorAssetI9n.feature
@@ -48,7 +48,6 @@ Feature: Job Engine Service - Asset 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 asset has been written when KuraMock gets refactored
 
   @teardown
   Scenario: Tear down test resources

diff --git a/...egration/src/test/resources/features/jobEngine/JobEngineServiceProcessorBundleI9n.feature b/...egration/src/test/resources/features/jobEngine/JobEngineServiceProcessorBundleI9n.feature
@@ -48,7 +48,6 @@ Feature: Job Engine Service - Bundle 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 bundle has been started when KuraMock gets refactored
 
   Scenario: Bundle Stop
 
@@ -69,7 +68,6 @@ Feature: Job Engine Service - Bundle 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 bundle has been stopped when KuraMock gets refactored
 
   @teardown
   Scenario: Tear down test resources

diff --git a/...gration/src/test/resources/features/jobEngine/JobEngineServiceProcessorCommandI9n.feature b/...gration/src/test/resources/features/jobEngine/JobEngineServiceProcessorCommandI9n.feature
@@ -48,7 +48,6 @@ Feature: Job Engine Service - Command 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 command has been executed when KuraMock gets refactored
 
   Scenario: Command Exec - JSON
 
@@ -69,7 +68,6 @@ Feature: Job Engine Service - Command 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 command has been executed when KuraMock gets refactored
 
   @teardown
   Scenario: Tear down test resources

diff --git a/...n/src/test/resources/features/jobEngine/JobEngineServiceProcessorConfigurationI9n.feature b/...n/src/test/resources/features/jobEngine/JobEngineServiceProcessorConfigurationI9n.feature
@@ -48,7 +48,6 @@ Feature: Job Engine Service - Configuration 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 configuration has been applied when KuraMock gets refactored
 
   Scenario: Configuration Put - JSON
 
@@ -69,7 +68,6 @@ Feature: Job Engine Service - Configuration 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 configuration has been applied when KuraMock gets refactored
 
   @teardown
   Scenario: Tear down test resources

diff --git a/...ration/src/test/resources/features/jobEngine/JobEngineServiceProcessorKeystoreI9n.feature b/...ration/src/test/resources/features/jobEngine/JobEngineServiceProcessorKeystoreI9n.feature
@@ -50,7 +50,6 @@ 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 certificate has been installed when KuraMock gets refactored
 
   Scenario: Keystore Keypair Create Processor
 
@@ -76,7 +75,6 @@ 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 keypair has been created when KuraMock gets refactored
 
   Scenario: Keystore Item Delete Processor
 
@@ -98,7 +96,6 @@ 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 deleted when KuraMock gets refactored
 
   @teardown
   Scenario: Tear down test resources