[CNTCTSAPP-128] Provide a minimal set of labels for the contacts-v8 app Created: 06/Dec/23  Updated: 13/Dec/23

Status: In Progress
Project: Contacts App
Component/s: None
Affects Version/s: None
Fix Version/s: 2.0.0

Type: Task Priority: Neutral
Reporter: Christoph Meier Assignee: Christoph Meier
Resolution: Unresolved Votes: 0
Labels: TAE
Remaining Estimate: Not Specified
Time Spent: 0.25d
Original Estimate: Not Specified

Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Date of First Response:
Work Started:

 Description   

Context

afaik, contacts-v8 never gets bundled in prod.
It was build when M6-UI-fwk was built as a showcase / developer-app.

Now we also will use contacts-v8 in self-tests of the "core" test-framework.
For this we need to ensure a minimal set of labels.

Instead of adding a decorator in "test fixtire module" - we rather should provide these labels in the contacts module itself



 Comments   
Comment by Christoph Meier [ 08/Dec/23 ]

rkovarik
Reason is a bit complicated ...
In the context of MGNLTEST-449 - which will end up with two branches for the core-TF - we aim to run core-TF-self-tests like this:

  • core-TF release/1.4 vs. 6.2-webapp
  • core-TF main vs. 6.3-webapp.

core-TF-self-tests heavily rely on contacts jcr workspace.
Tons of core-TF-self-tests operate on the jcr-workspace contacts - which currently is not present on dx-core-test-webapp::6.3. And there are also a few tests which directly open on the contacts-app.

So ... I was adding the module contacts-app to the dx-core-test-webapp (on master/6.3); also unhiding contacts-8 (with this commit).

Unfortunately, when running core-TF-self-test vs. dx-core-test-webapp::6.3, we still have a lot of errors.
We will fix them. And while doing this, I will decide whether contacts-v8 still is the "good solution" for these self-tests. or if it's not.
In any case: I want to keep JCR-workspace and thus module contacts-app on dx-core-test-webapp::6.3.
And adding the labels to contacts-v8, maybe, it was useless, but it shouldn't hurt.

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