Details
-
Story
-
Resolution: Fixed
-
Neutral
-
None
-
None
-
-
Empty show more show less
-
Yes
-
Add-Ons 46, Add-Ons 47
-
5
Description
Aborting a test may cause potential issues in the data consistency for us. Aborting a test allows users to edit that particular test, meaning, the previous data will become stale and should be wiped out. However, there is a potential chance that the workflow jobs will be running at the time we have removed that data and the running job may have processed/cached it already which will lead to an inconsistent test result. In order to avoid that, we need to make sure we remove the data as well as start the previously aborted test with new UUID so that we make sure we don't mix data.
AC
- use the awsTestId custom property to fetch and to send timeline-results data from/to DynamoDB
- On 'abort action'
Wipe data in S3- Wipe data in Dynamo
- flush the test-results and analytics caches
- Check the state of the node in the 'start action' test
- If the state is 'ABORTED'
Wipe data in S3 (to make sure)- regenerate the awsTestId
- If the state is 'ABORTED'
Checklists
Acceptance criteria
Attachments
Issue Links
- is cloned by
-
ABTEST-258 Deleting test wipes out the data in the cloud
-
- Closed
-