[MGNLTEST-33] Attempt to make functional tests repeatable and independent Created: 07/Feb/20 Updated: 27/Oct/22 |
|
| Status: | Open |
| Project: | Magnolia Test Framework |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Neutral |
| Reporter: | Jorge Franco | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | QA&Testing | ||
| 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: | core-TF-features-bugs-improvements |
| Team: |
| Description |
|
When running functional tests, the state of the application can change, for example JCR can be modified. We have annotation @Cleanup to handle with changes in JCR. But developers have to remember to add the annotation, or maybe something unexpected can change. So, to be sure that each test starts in the same state of the application, we have to try find a way to 'cleanup' the state of the application between tests. |