[ABTEST-180] Aborting a test wipes out the data in the cloud Created: 22/Apr/20 Updated: 24/Sep/20 Resolved: 17/Sep/20 |
|
| Status: | Closed |
| Project: | A/B Testing |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 1.0 |
| Type: | Story | Priority: | Neutral |
| Reporter: | Ilgun Ilgun | Assignee: | Andrei Ichimescu |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Template: |
|
||||||||
| Acceptance criteria: |
Empty
|
||||||||
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
||||||||
| Documentation update required: |
Yes
|
||||||||
| Epic Link: | ABTEST MVP | ||||||||
| Sprint: | Add-Ons 46, Add-Ons 47 | ||||||||
| Story Points: | 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
|