diff --git a/devRun.sh b/devRun.sh
deleted file mode 100755
index 9050730745e0d7cca5106aa30a60d0ed46941414..0000000000000000000000000000000000000000
--- a/devRun.sh
+++ /dev/null
@@ -1,10 +0,0 @@
-#!/bin/bash
-
-# This is the run command
-./gradlew regressionSuite \
-  -PbaseUrl="http://localhost:8081" \
-  -Dcucumber.tags="@rest, ~@wip" \
-  -Dcourgette.threads=10 \
-  -Dcourgette.runLevel=Scenario \
-  -Dcourgette.rerunFailedScenarios=false \
-  -Dcourgette.rerunAttempts=1
\ No newline at end of file
diff --git a/features/trustedInfoExport.feature b/features/trustedInfoExport.feature
deleted file mode 100644
index 3d953328f5adfa5a8a8eb8b9a73b9afef4a95b38..0000000000000000000000000000000000000000
--- a/features/trustedInfoExport.feature
+++ /dev/null
@@ -1,45 +0,0 @@
-As user of an external system
-I want to have an exported trusted result of the policy in JSON-LD format
-So I am able to verify the result of policy evaluation
-
-Scenario: Execute task for exporting data from external resource
-Given the environment configured for running policy to export
-And the the DID published somewhere
-When I execute the task 
-And the task contains the actual http url to execute
-And the finalizer policy contains signing the data logic
-Then I get a successful response
-And the response contains task id
-
-Scenario: Execute task for exporting data from the policy evaluation
-Given the environment configured for running policy to export
-When I execute the task
-And the task contains the the request policy to evaluate
-And the finalizer policy contains signing the data logic
-Then I get a successful response
-And the response contains task id
-
-Scenario: Export of the policy evaluation result
-Given value exists inside of the cache
-And the format of the value is in JSON-LD
-When I execute policy export endpoint
-And the request contains task id
-Then I get a successful response
-And the response contains the exported document
-
-
-- DID document should be in a format of the DID Web
-- Generating VC / VP should be configured as a policy of plugin
-- Export configuration we need to put as a task config (mark policy as export).
-- Should be possible to use export a list of policies and get a one VP of all. 
-- Have an export configuration of the task list
-- Generating the hash is an open question ?
-- Generation of VP as a separate container ?
-
->> 
-When a task generated
-And I setup an export config
-Then I need for VP a DID which signs VP
-When I setup an export, DID can be generated automatically
-Then I configure a hashicorp Valut with keypair for signing
-And put the DID document should be put inside of the cache
diff --git a/features/trustedInfoImport.feature b/features/trustedInfoImport.feature
deleted file mode 100644
index 145b098d70f80c39b185f652cfa83eb72da66957..0000000000000000000000000000000000000000
--- a/features/trustedInfoImport.feature
+++ /dev/null
@@ -1,16 +0,0 @@
-As user 
-I want to import value to the cache and trust to the imported content
-So I can then process the trusted data
-
-Scenario: Import data
-Given DID documents are published
-And JSON transformations policy is published
-When I send a request to import
-And the request contains JSON-LD data
-And the request contains allowed DIDs list
-And the request contains import interval
-And the request contains http sources to import
-When I get a successful response
-When I evaluate the policy to get result from the cache
-Then I get a response
-And the response contains transformed data
diff --git a/src/test/resources/features/tsa/signer/v1/credential/proof/POST.feature b/src/test/resources/features/tsa/signer/v1/credential/proof/POST.feature
index 07586ba0c53b0637fad96e11b97b5026f155faeb..19b959c569f75e35d2c6fa2e21bcbbb16082411e 100644
--- a/src/test/resources/features/tsa/signer/v1/credential/proof/POST.feature
+++ b/src/test/resources/features/tsa/signer/v1/credential/proof/POST.feature
@@ -32,9 +32,8 @@ Feature: API - TSA - Signer credential proof - v1/credential/proof POST
     And the response is valid according to the {Signer_CredentialProof_schema.json} REST schema
     And the field {proof.verificationMethod} has the value {did:web:gaiax.vereign.com:tsa:policy:policy:example:returnDID:1.0:evaluation#key1}
 
-  @wip @bug-signer-#13 @negative
+  @negative
   Scenario: TSA - validate credential proof with empty body - Negative
     When I set the following request body {{}}
     When I create credential proof via TSA Signer API
-    And the status code should be {400}
-    And the field {message} has the value {missing required payload}
+    And the status code should be {400}
\ No newline at end of file
diff --git a/src/test/resources/features/tsa/signer/v1/presentation/proof/POST.feature b/src/test/resources/features/tsa/signer/v1/presentation/proof/POST.feature
index bb8c99f690102f9ec8c05f2e6f66fd08962a5b99..94b03ca3ae119ad86c6c3bdb6109ec7b673f0fea 100644
--- a/src/test/resources/features/tsa/signer/v1/presentation/proof/POST.feature
+++ b/src/test/resources/features/tsa/signer/v1/presentation/proof/POST.feature
@@ -32,9 +32,8 @@ Feature: API - TSA - Signer presentation proof - v1/presentation/proof POST
     And the response is valid according to the {Signer_PresentationProof_schema.json} REST schema
     And the field {proof.verificationMethod} has the value {did:web:gaiax.vereign.com:tsa:policy:policy:example:returnDID:1.0:evaluation#key1}
 
-  @wip @bug-signer-#13 @negative
+  @negative
   Scenario: TSA - validate presentation proof with empty body - Negative
     When I set the following request body {{}}
     When I create presentation proof via TSA Signer API
-    And the status code should be {400}
-    And the field {message} has the value {missing required payload}
+    And the status code should be {400}
\ No newline at end of file