[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:
Key
Summary
Type
Status
Assignee
CONTTAGS-123 Implementation Sub-task To Do  
CONTTAGS-124 Review Sub-task To Do  
CONTTAGS-125 Pre-Integration QA Sub-task To Do  
CONTTAGS-126 QA Sub-task To Do  
Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Team: Foundation

 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.
This ticket is only about defining a scenario, maybe a few scenarios.

The old (deleted) test was mainly testing keyboard functions (things like tagByShortcut, tagMultipleItems, etc.).
New scenario should cover a typical use case e.g. of an author.

You may want to read The process of creating int. and functional tests - simplified upfront.


Generated at Mon Feb 12 00:25:11 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.