[ABTEST-77] Introduce a component (typical manager but not manager) Created: 13/Aug/19 Updated: 17/Oct/19 Resolved: 08/Oct/19 |
|
| 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: | Ilgun Ilgun |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| 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)
|
| Epic Link: | Tests generation |
| Sprint: | Add-Ons 22 |
| Story Points: | 8 |
| Description |
|
This component will sit in between everything and orchestrate tests in general regarding various topics e.g. test creation, state changes (paused, running, etc) as well as filter chain can directly query the state of a 'nodePath' from this component.
|