dashboard
dashboard copied to clipboard
E2E for project/namespace list view
Test cases for namespace filtering
Basic filtering
- When a user selects a namespace in the top nav of cluster explorer, then goes to the list view of a namespaced resource such as Deployments, confirm that only resources in the selected namespaces are listed.
- After refreshing the page, the namespace filter is still persisted.
Adding and deleting namespaces and projects
- When the user creates or deletes a namespace, the Projects/Namespaces list view is immediately updated.
- When the user creates or deletes a project, the Projects/Namespaces list view is immediately updated.
- When a user creates a namespace in a project, the list view immediately updates to show the namespace in the project.
- When a project is deleted, and the user chooses to delete the namespaces within the project, both the project and the namespaces are removed from the list view.
- When a project is deleted, and the user chooses not to delete the namespaces within the project, the namespaces are moved to "Not in a Project."
System namespaces
- rancher/dashboard#7472 has additional conditions but for advanced purposes
- When the user selects "Only System Namespaces" in the top nav, only namespaces in the System project are shown.
- When the user selects "Only User Namespaces" in the top nav, the System project is hidden.
Namespaces not in a project
- The "Not in a project" group of namespaces is visible to admins and cluster owners, but not project owners or project members.
- When a cluster owner or admin deletes a project, they can choose to delete the namespaces inside it or not. After the project is deleted, they can see the namespaces that used to be in the project grouped under "Not in a Project."
- When a project owner or project member deletes a project, they have to delete all the namespaces in the project as well.
- When a project owner or project member turns on the developer tools in the user preferences, they can see any namespaces that are not in a project.
- Only admins and cluster owners can create a namespace that is not in a project.
Empty projects
- When the user selects "All Namespaces" or "Only User Namespaces" in the top nav, the Projects/Namespaces list page also includes empty projects.
- When the user selects specific projects or namespaces in the top nav, empty namespaces are not shown.
The Epinio namespace filter is covered by https://github.com/epinio/epinio-end-to-end-tests/issues/213
added some test cases for Workspaces (Fleet)
Added some test cases for Harvester
I've updated the list of tests based on the project structure.
Upon discussion with @catherineluse, we need to split this ticket in manageable chunks, namely 3.
I'll split this into smaller tickets.
Please keep in mind that @manuelecarlini is redesigning some points and may be convenient to match possible reworks with the list above.