BC-3844 - upgrade to Vue3 and Vuetify3 (#449)

To be able to use the latest features of Vue we want to upgrade the frontend to Vue 3. Doing that we have to upgrade to Vuetify 3. --------- Co-authored-by: Uzaeir Khan <[email protected]>
hpi-schul-cloud · Feb 27, 2024 · 3c54ca3 · 3c54ca3
1 parent 0e59301
commit 3c54ca3
Show file tree

Hide file tree

Showing 15 changed files with 3,423 additions and 2,012 deletions.
diff --git a/features/courses/searchCourse.feature b/features/courses/searchCourse.feature
@@ -1,27 +1,27 @@
 @courses @searchCourse @stableTest @courses_and_topics
 Feature: Set of tests to search courses
 
-    Background: User opens Schul-cloud homepage Website
-        Given user arrives on the Schul-Cloud homepage
+	Background: User opens Schul-cloud homepage Website
+		Given user arrives on the Schul-Cloud homepage
 
-    @searchCourseAndFindOne
-    Scenario Outline: As a user, I want to be able to search a course and find them.
-        Given <userRole> logs in with email '<username>' and password '<password>'
-        And <userRole> goes to rooms-overview
-        When <userRole> enters course name '<courseName>' into search field
-        And <userRole> should see that course with name '<courseName>' is visible on the list
-        Examples:
-            | userRole | username                         | password       | courseName |
-            | teacher  | karl.teacher.qa@schul-cloud.org  | Schulcloud1qa! | Biologie   |
-            | student  | amelia.strobl.qa@schul-cloud.org | Schulcloud1qa! | German     |
+	@searchCourseAndFindOne
+	Scenario Outline: As a user, I want to be able to search a course and find them.
+		Given <userRole> logs in with email '<username>' and password '<password>'
+		And <userRole> goes to rooms-overview
+		When <userRole> enters course name '<courseName>' into search field
+		And <userRole> should see that course with name '<courseName>' is visible on the list
+		Examples:
+			| userRole | username                         | password       | courseName |
+			| teacher  | karl.teacher.qa@schul-cloud.org  | Schulcloud1qa! | Biologie   |
+			| student  | amelia.strobl.qa@schul-cloud.org | Schulcloud1qa! | German     |
 
-    @searchCourseAndDontFindOne
-    Scenario Outline: As a user, I want to be able to search a course and do not find them.
-        Given <userRole> logs in with email '<username>' and password '<password>'
-        And <userRole> goes to rooms-overview
-        When <userRole> enters course name '<courseName>' into search field
-        Then <userRole> should see that course with name '<courseName>' is not visible on the list
-        Examples:
-            | userRole | username                         | password       | courseName |
-            | teacher  | karl.teacher.qa@schul-cloud.org  | Schulcloud1qa! | Mathematik |
-            | student  | amelia.strobl.qa@schul-cloud.org | Schulcloud1qa! | Deutsch    |
+	@searchCourseAndDontFindOne
+	Scenario Outline: As a user, I want to be able to search a course and do not find them.
+		Given <userRole> logs in with email '<username>' and password '<password>'
+		And <userRole> goes to rooms-overview
+		When <userRole> enters course name '<courseName>' into search field
+		Then <userRole> should see that course with name '<courseName>' is not visible on the list
+		Examples:
+			| userRole | username                         | password       | courseName |
+			| teacher  | karl.teacher.qa@schul-cloud.org  | Schulcloud1qa! | Mathematik |
+			| student  | amelia.strobl.qa@schul-cloud.org | Schulcloud1qa! | Deutsch    |
diff --git a/features/management_students/createStudent.feature b/features/management_students/createStudent.feature
@@ -15,7 +15,7 @@ Feature: Set of tests to create students
 		And <userRole> sees that student with email '<studentEmail>' is visible on the list
 		And <userRole> manually submits consent for user with e-mail '<studentEmail>', thus generates a random password for him
 		And <userRole> logs out
-        And user arrives on the Schul-Cloud homepage
+		And user arrives on the Schul-Cloud homepage
 		And student logs in with email '<studentEmail>' and password genarated by admin during manual submission of consent
 		Then student should see that data protection is already accepted and performs first login actions: password change '<newPasswordStudent>'
 		Examples:

diff --git a/features/management_teachers/createTeacher.feature b/features/management_teachers/createTeacher.feature
@@ -14,5 +14,5 @@ Feature: Set of tests to create teachers
 		When <userRole> set teacher firstname '<firstName>', lastname '<lastName>', email '<teacherEmail>'
 		And <userRole> sees that teacher with email '<teacherEmail>' is visible on the list
 		Examples:
-			| userRole | firstName  | lastName   | teacherEmail					| username                     | password       |
+			| userRole | firstName  | lastName   | teacherEmail                 | username                     | password       |
 			| admin    | Theophilus | Hermelates | t.hermelates@schul-cloud.org | kai.admin.qa@schul-cloud.org | Schulcloud1qa! |
diff --git a/features/navigation_bar_left/leftNavigationBar.feature b/features/navigation_bar_left/leftNavigationBar.feature
@@ -1,66 +1,64 @@
 @leftNavigationBar @stableTest @navi_user_settings
 Feature: Test set to check the left side menu items
 
-    Background:
-        Given user arrives on the Schul-Cloud homepage
+	Background:
+		Given user arrives on the Schul-Cloud homepage
 
-    @adminTeacherClicksLeftMenuItems @e2eCore
-    Scenario Outline: As a user, I want to be able to click the left menu items
-        Given <userRole> logs in
-        Then <userRole> clicks left navigation item 'logo'
-        And <userRole> clicks left navigation item 'dashboard'
-        And <userRole> clicks left navigation item 'teams'
-        And <userRole> clicks left navigation item 'homework'
-        And <userRole> clicks left navigation item 'rooms-overview'
-        And <userRole> clicks left navigation item 'asked homework'
-        And <userRole> clicks left navigation item 'private homework'
-        And <userRole> clicks left navigation item 'archived homework'
-        And <userRole> clicks left navigation item 'files'
-        And <userRole> clicks left navigation item 'my files'
-        And <userRole> clicks left navigation item 'course files'
-        And <userRole> clicks left navigation item 'team files'
-        And <userRole> clicks left navigation item 'shared files'
-        And <userRole> clicks left navigation item 'news'
-        And <userRole> clicks left navigation item 'calendar'
-        And <userRole> clicks left navigation item 'addons'
-        And <userRole> clicks left navigation item 'administration'
-        And <userRole> should see that all sub menu items are visible: '<tabsList>'
-        And <userRole> clicks left navigation item 'helparea'
-        And <userRole> clicks left navigation item 'helparticle'
-        And <userRole> clicks left navigation item 'contact'
-        # TODO nuxt pages - the navigation structure is different,
-        #  therefor leave it for last page otherwise the other pages won't be found
-        And <userRole> clicks left navigation item 'content'
-        Examples:
-            | userRole | tabsList                                       |
-            | teacher  | SCHÜLER:INNEN, LEHRER:INNEN, KLASSEN           |
-            | admin    | SCHÜLER, LEHRER, KURSE, KLASSEN, TEAMS, SCHULE |
+	@adminTeacherClicksLeftMenuItems @e2eCore
+	Scenario Outline: As a user, I want to be able to click the left menu items
+		Given <userRole> logs in
+		Then <userRole> clicks left navigation item 'logo'
+		And <userRole> clicks left navigation item 'dashboard'
+		And <userRole> clicks left navigation item 'teams'
+		And <userRole> clicks left navigation item 'homework'
+		And <userRole> clicks left navigation item 'rooms-overview'
+		And <userRole> clicks left navigation item 'asked homework'
+		And <userRole> clicks left navigation item 'private homework'
+		And <userRole> clicks left navigation item 'archived homework'
+		And <userRole> clicks left navigation item 'files'
+		And <userRole> clicks left navigation item 'my files'
+		And <userRole> clicks left navigation item 'course files'
+		And <userRole> clicks left navigation item 'team files'
+		And <userRole> clicks left navigation item 'shared files'
+		And <userRole> clicks left navigation item 'news'
+		And <userRole> clicks left navigation item 'calendar'
+		And <userRole> clicks left navigation item 'administration'
+		And <userRole> should see that all sub menu items are visible: '<tabsList>'
+		And <userRole> clicks left navigation item 'helparea'
+		And <userRole> clicks left navigation item 'helparticle'
+		And <userRole> clicks left navigation item 'contact'
+		# TODO nuxt pages - the navigation structure is different,
+		#  therefor leave it for last page otherwise the other pages won't be found
+		And <userRole> clicks left navigation item 'content'
+		Examples:
+			| userRole | tabsList                                       |
+			| teacher  | SCHÜLER:INNEN, LEHRER:INNEN, KLASSEN           |
+			| admin    | SCHÜLER, LEHRER, KURSE, KLASSEN, TEAMS, SCHULE |
 
-    @studentClicksLeftMenuItems
-    Scenario Outline: As a user, I want to be able to click the left menu items
-        Given student logs in
-        Then <userRole> clicks left navigation item 'logo'
-        And <userRole> clicks left navigation item 'dashboard'
-        And <userRole> clicks left navigation item 'rooms-overview'
-        And <userRole> clicks left navigation item 'teams'
-        And <userRole> clicks left navigation item 'homework'
-        And <userRole> clicks left navigation item 'asked homework'
-        And <userRole> clicks left navigation item 'private homework'
-        And <userRole> clicks left navigation item 'archived homework'
-        And <userRole> clicks left navigation item 'files'
-        And <userRole> clicks left navigation item 'my files'
-        And <userRole> clicks left navigation item 'course files'
-        And <userRole> clicks left navigation item 'team files'
-        And <userRole> clicks left navigation item 'shared files'
-        And <userRole> clicks left navigation item 'news'
-        And <userRole> clicks left navigation item 'calendar'
-        And <userRole> clicks left navigation item 'addons'
-        And <userRole> clicks left navigation item 'helparea'
-        And <userRole> clicks left navigation item 'helparticle'
-        And <userRole> clicks left navigation item 'contact'
-        # TODO nuxt pages - the navigation structure is different,
-        #  therefor leave it for last page otherwise the other pages won't be found
-        And <userRole> clicks left navigation item 'content'
-        Examples:
-            | userRole |
-            | student  |
+	@studentClicksLeftMenuItems
+	Scenario Outline: As a user, I want to be able to click the left menu items
+		Given student logs in
+		Then <userRole> clicks left navigation item 'logo'
+		And <userRole> clicks left navigation item 'dashboard'
+		And <userRole> clicks left navigation item 'rooms-overview'
+		And <userRole> clicks left navigation item 'teams'
+		And <userRole> clicks left navigation item 'homework'
+		And <userRole> clicks left navigation item 'asked homework'
+		And <userRole> clicks left navigation item 'private homework'
+		And <userRole> clicks left navigation item 'archived homework'
+		And <userRole> clicks left navigation item 'files'
+		And <userRole> clicks left navigation item 'my files'
+		And <userRole> clicks left navigation item 'course files'
+		And <userRole> clicks left navigation item 'team files'
+		And <userRole> clicks left navigation item 'shared files'
+		And <userRole> clicks left navigation item 'news'
+		And <userRole> clicks left navigation item 'calendar'
+		And <userRole> clicks left navigation item 'helparea'
+		And <userRole> clicks left navigation item 'helparticle'
+		And <userRole> clicks left navigation item 'contact'
+		# TODO nuxt pages - the navigation structure is different,
+		#  therefor leave it for last page otherwise the other pages won't be found
+		And <userRole> clicks left navigation item 'content'
+		Examples:
+			| userRole |
+			| student  |
diff --git a/features/teams/deleteTeam.feature b/features/teams/deleteTeam.feature
@@ -1,17 +1,17 @@
 @teams @e2eCore @stableTest @tasks_and_other
 Feature: Set of tests to delete teams
 
-    Background: User opens Schul-cloud homepage Website
-        Given user arrives on the Schul-Cloud homepage
+	Background: User opens Schul-cloud homepage Website
+		Given user arrives on the Schul-Cloud homepage
 
-    @deleteTeam
-    Scenario Outline: As a user, I want to be able to delete a team
-        Given <userRole> logs in with email '<userName>' and password '<password>'
-        Then <userRole> goes to Teams Page
-        And <userRole> sees that team with name '<teamName>' is visible on the list
-        When <userRole> chooses team with name '<teamName>'
-        And <userRole> clicks on Delete-team button
-        Then <userRole> sees that team with name '<teamName>' is not visible on the list
-        Examples:
-            | userRole | userName                        | password       | teamName   |
-            | teacher  | karl.teacher.qa@schul-cloud.org | Schulcloud1qa! | Musik      |
+	@deleteTeam
+	Scenario Outline: As a user, I want to be able to delete a team
+		Given <userRole> logs in with email '<userName>' and password '<password>'
+		Then <userRole> goes to Teams Page
+		And <userRole> sees that team with name '<teamName>' is visible on the list
+		When <userRole> chooses team with name '<teamName>'
+		And <userRole> clicks on Delete-team button
+		Then <userRole> sees that team with name '<teamName>' is not visible on the list
+		Examples:
+			| userRole | userName                        | password       | teamName |
+			| teacher  | karl.teacher.qa@schul-cloud.org | Schulcloud1qa! | Musik    |
diff --git a/features/teams/editTeam.feature b/features/teams/editTeam.feature
@@ -1,24 +1,24 @@
 @teams @e2eCore @stableTest @tasks_and_other
 Feature: Set of tests to edit teams
 
-    Background: User opens Schul-cloud homepage Website
-        Given user arrives on the Schul-Cloud homepage
+	Background: User opens Schul-cloud homepage Website
+		Given user arrives on the Schul-Cloud homepage
 
-    @editTeam
-    Scenario Outline: As a user, I want to be able to edit a team
-        Given <userRole> logs in with email '<userName>' and password '<password>'
-        Then <userRole> goes to Teams Page
-        And <userRole> sees that team with name '<teamName>' is visible on the list
-        When <userRole> chooses team with name '<teamName>'
-        And <userRole> clicks on Edit-team button
-        And <userRole> changes name of Team '<changeName>'
-        And <userRole> changes team description '<description>'
-        And <userRole> chooses team colour '<colour>'
-        And <userRole> clicks on Save-changes in team button
-        And <userRole> goes to Teams Page
-        Then <userRole> sees that team with name '<changeName>' is visible on the list
-        And <userRole> should see that team name '<changeName>' with description correctly displayed '<description>'
-        And <userRole> should see team with name '<changeName>' has colour '<colour>'
-        Examples:
-            | userRole | userName                        | password       | teamName   | colour | changeName | description |
-            | teacher  | karl.teacher.qa@schul-cloud.org | Schulcloud1qa! | Musik      | green  | Sport      | I LIKE IT   |
+	@editTeam
+	Scenario Outline: As a user, I want to be able to edit a team
+		Given <userRole> logs in with email '<userName>' and password '<password>'
+		Then <userRole> goes to Teams Page
+		And <userRole> sees that team with name '<teamName>' is visible on the list
+		When <userRole> chooses team with name '<teamName>'
+		And <userRole> clicks on Edit-team button
+		And <userRole> changes name of Team '<changeName>'
+		And <userRole> changes team description '<description>'
+		And <userRole> chooses team colour '<colour>'
+		And <userRole> clicks on Save-changes in team button
+		And <userRole> goes to Teams Page
+		Then <userRole> sees that team with name '<changeName>' is visible on the list
+		And <userRole> should see that team name '<changeName>' with description correctly displayed '<description>'
+		And <userRole> should see team with name '<changeName>' has colour '<colour>'
+		Examples:
+			| userRole | userName                        | password       | teamName | colour | changeName | description |
+			| teacher  | karl.teacher.qa@schul-cloud.org | Schulcloud1qa! | Musik    | green  | Sport      | I LIKE IT   |