[CONTTAGS-122] Define (a) meaningful scenario to test content tags Created: 19/Jul/22 Updated: 19/Jul/22 |
|
| Status: | Open |
| Project: | Content Tags |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Neutral |
| Reporter: | Christoph Meier | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Σ Remaining Estimate: | Not Specified | Remaining Estimate: | Not Specified |
| Σ Time Spent: | Not Specified | Time Spent: | Not Specified |
| Σ Original Estimate: | Not Specified | Original Estimate: | Not Specified |
| Sub-Tasks: |
|
|||||||||||||||||||||||||
| Template: | ||||||||||||||||||||||||||
| Acceptance criteria: |
Empty
|
|||||||||||||||||||||||||
| Task DoR: |
Empty
|
|||||||||||||||||||||||||
| Team: |
| Description |
|
In context of 6.3/master branch reconciliation - we had to remove the old test it.info.magnolia.eeintegrationtests.uitest.TaggingUITest. We should re-implement at least one meaningful scenario. The old (deleted) test was mainly testing keyboard functions (things like tagByShortcut, tagMultipleItems, etc.). You may want to read The process of creating int. and functional tests - simplified upfront. |