diff --git a/features/distributedCache.feature b/features/distributedCache.feature deleted file mode 100644 index 87aa9dbc07f45eac46aabdaaae045bfd9ae2c146..0000000000000000000000000000000000000000 --- a/features/distributedCache.feature +++ /dev/null @@ -1,20 +0,0 @@ -As policy administrator -I want to have distributed cache feature provided -So I am able to use cache functionality in my custom policies - -Scenario: Working with cache -Given one policy to set the value in the cache is uploaded to the system -And the second policy to get the value from the cache is uploaded to the system as well -When I evaluate policy to set the value in the cache -And get a successful response -When I evaluate policy to get the value from the cache -Then I get a successful response -And response body is not empty - - -Acceptance criteria: -- The plugin for rego language to get/set values is ready to use -- The working example how to use the plugin -- Green test based on example commited to the system - - diff --git a/features/executeTask.feature b/features/executeTask.feature index b2c90306f790bcf715ae26b47838dc0b1a56d0b1..933802a754cc5b519916eaafb38ae98456faedfa 100644 --- a/features/executeTask.feature +++ b/features/executeTask.feature @@ -1,12 +1,12 @@ As user -I want to evaluate the policy asyncronously +I want to evaluate the policy asynchronously So I am able to execute the developed Rego code in the future non-blocking Scenario: Execute the task during evaluating policy Given long running policy is uploaded to the system And the task template is uploaded to the system -When I evaluate the policy asyncronously -And the task template is specifyed as an input +When I evaluate the policy asynchronously +And the task template is specified as an input When I get successful response And the response contains taskId @@ -16,9 +16,9 @@ When I request the result of execution And request contains the taskId And the task has finished Then I get successful response -And esponse contains the result of execution of the policy +And response contains the result of execution of the policy Acceptance criteria: -- HTTP endpoints to evalute the policy asyncronously and get the result -- example of long-running policy commited to Git repo -- Green test based on example commited to the system +- HTTP endpoints to evaluate the policy asynchronously and get the result +- example of long-running policy committed to Git repo +- Green test based on example committed to the system diff --git a/features/persistance.feature b/features/persistance.feature index d77d0055a79b6d5d5bfcaca29ecff8ae72c8ff5d..e6f0c26754cfbae1d26ddd358a51c1b359a31d48 100644 --- a/features/persistance.feature +++ b/features/persistance.feature @@ -13,5 +13,5 @@ And response body is not empty Acceptance criteria: - plugin for rego language to set/query values is ready to use -- example of usage of the plugin commited to the system -- green tests based on example commited to the system \ No newline at end of file +- example of usage of the plugin committed to the system +- green tests based on example committed to the system \ No newline at end of file