[Web] e2e tests for Administration Settings part 1

[exalate-issue-sync]

Description

Note. before you begin to implement test, please assign a specific test from list to yourself so that you do not do the same work

User Stories

• As an admin I want Administration Settings I can rely on because I'm resposible to support all users at my school.

Value

Acceptance Criteria

Following functionality should be covered by e2e (playwright) tests:

General

• logo upload (@lookacat )
• logo reset (@lookacat)
  note: content of the Info section doesn't need e2e tests.

Users

• lists users @lookacat
• filter @lookacat
  • filter by groups (part of different story)
  • filter by roles
• can create user (@lookacat)
• can open edit panel via quick action and via context menu (@lookacat)
• can edit
  • displayname
  • username
  • email
  • password
  • role @ScharfViktor
  • quota @ScharfViktor [test-only] edit personal quota test #8537
  • assigned groups
  • login allowed
  • login forbidden
• can use batch action for
  • delete
  • edit quota @ScharfViktor 100c7a9
  • add to groups (part of different story) [full-ci] Add remove/add users to group batch actions  #8553
  • remove from groups (part of different story) [full-ci] Add remove/add users to group batch actions  #8553

Groups

• lists groups
• can create group
• can delete group via context menu and batch action

Spaces

• lists spaces (including spaces that I'm not member of)
• can use context menu for
  • edit name
  • edit subtitle
  • edit quota
  • disable
  • enable
  • delete
• can use batch action for
  • edit quota
  • disable
  • enable
  • delete
• can list members in right sidebar

Definition of ready

[ ] everybody needs to understand the value written in the user story
[ ] acceptance criteria has to be defined
[ ] all dependencies of the user story need to be identified
[ ] feature should be seen from an end user perspective
[ ] user story has to be estimated
[ ] story points need to be less then 20

Definition of done

• Functional requirements
  [ ] functionality described in the user story works
  [ ] acceptance criteria are fulfilled
• Quality
  [ ] code review happened
  [ ] CI is green
  [ ] critical code received unit tests by the developer
  [ ] automated tests passed (if automated tests are not available, this test needs to be created and passed
• Non-functional requirements
  [ ] no sonar cloud issues

NOTE

This ticket is worked on in a timeboxed manner. Will be cloned with remaining tasks for the next sprint.

Agreed on 2 days for KOKO-Sprint 6.

[ScharfViktor]

before you begin to implement test, please assign a specific test from list to yourself so that you do not do the same work

[kulmann]

before you begin to implement test, please assign a specific test from list to yourself so that you do not do the same work

yes, good point. just put your github handles behind the list item in the ticket description.

[kulmann]

Closing here as it was worked on in a timeboxed manner in the last sprint. Please continue in #8601 for the next sprint (today, 13.03. until Friday 24.03.)