[MGNLTEST-63] Provide users, groups and roles used for functional tests (phase-1) Created: 15/Aug/19 Updated: 07/Jul/20 Resolved: 03/Sep/19 |
|
| Status: | Closed |
| Project: | Magnolia Test Framework |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Neutral |
| Reporter: | Christoph Meier | Assignee: | Christoph Meier |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Template: |
|
||||||||||||||||
| Acceptance criteria: |
Empty
|
||||||||||||||||
| Task DoR: |
Empty
|
||||||||||||||||
| Epic Link: | core-TF-features-bugs-improvements | ||||||||||||||||
| Description |
Refined versionWhile trying to resolve the ticket for the original scope, it turned out, that users, groups and roles are not sufficient to provide acces to the "most prominent content app" (such as pages, assets, contacts, categorization) for paige (a content editor) and pablo (a content publisher). With the current state Magnolia ce and dx-core, there is also the need to decorate the apps on:
The group of interest has decided, it must be possible to provide access to content apps by defining users, groups and roles only, and that we should not decorate the apps to provide access for the test personas. For the functional tests this means, atm, we cannot use paige (the editor) and pablo (the publisher), however, we still can use armin (a superuser enabled guy). Refined scope
OLD versionContextFor many functional tests (to be implemented as UI tests), we need distinct users (avoiding to run all the tests with superuser or eric). The List of required functional tests already lists such users, however, the list must be refined and properly specified, and finally we need "bootstrappable" content providing these users (groups and roles). It is worth to mention, that the Magnolia demo modules (travel-demo, etc.) bootstraps a bunch of users, roles and groups (= security items). Since the security items provided by the travel-demo are a bit messy, functional tests should not rely on them. ScopeDescribe and define the users (and groups and roles) - the security items - and produce bootstraps for the following personas
Acceptance criteria
|
| Comments |
| Comment by Christoph Meier [ 20/Aug/19 ] |
Results for the refined scope
|
| Comment by Christoph Meier [ 03/Sep/19 ] |
|
comments provided by Mika in slack:
I will do this on the follow-up ticket. This one only creates armin, where the bootstrap already has been cleaned-up.
I will check this, and provide an appropriate description of the next personas to define (paige, pablo, etc. pp)
|