[MGNLTEST-365] add "editable-test-user" to UserRepository, SaasTestsuiteConfiguration Created: 28/Nov/22  Updated: 10/Nov/23  Resolved: 08/Nov/23

Status: Closed
Project: Magnolia Test Framework
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Critical
Reporter: Christoph Meier Assignee: Unassigned
Resolution: Resolved Votes: 0
Labels: TPR-E2E
Remaining Estimate: Not Specified
Time Spent: 0.75d
Original Estimate: Not Specified

Issue Links:
dependency
depends upon MGNLTEST-320 Add test-users EDITOR, PUBLISHER, DEV... Open
Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Epic Link: saas-TF-extended-test-user-support
Team: Foundation
Work Started:
Approved:
Yes

 Description   

Add the new user to

  • info.magnolia.test.saas.infra.subscription.UserRepository
  • info.magnolia.test.saas.SaasTestsuiteConfiguration

Add self test which ...

  • not yet sure what the self-test- should do ...

The saas-TF should be able to

  • create a new sub - as we did until now
    • Optionally - in the process of creating the sub with its users - saas-infra-connectors also allows to add an additional user to the sub - The "editable-test-user"
    • Or expose a method to SaasTestsuiteInitializer to add the editable user (also see MGNLTEST-373) - since not every test-suite may need that "editable-test-user"

Implementation details

As the test user needs to be assigned to the subscription with a given role, this task can be considered a particular case of MGNLTEST-320.

 

Issue:
When adding a new user to a sub 
And using this user to login
Then the UI ask to agree in "Terms in conditions"

... which currently screws up tests. Right now on UI tests we can not properly handle agree in "Terms in conditions".
nguyen.phung told me he would know how to call the API to ensure such user must not agree in terms&conditions


Generated at Mon Feb 12 07:48:13 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.