-
Epic
-
Resolution: Done
-
Major
-
None
-
None
-
None
-
QE - Testing Phase 1
-
False
-
-
False
-
Testable
-
No
-
To Do
-
No
-
Pending
-
None
-
-
Doc: https://docs.google.com/document/d/1pxzG5579nWdhZyckRk0Z40Y7rjo4fqhhEmYYqV4armQ/edit?usp=sharing
| Test Case 1 | Comments | |
|---|---|---|
| 1 | User with role <user_role> can create a Workbench with Accelerator configuration <accelerator_config> | Golden Path |
| 2 | User can add a Model Server using Accelerators with configuration <accelerator_config> | Golden Path |
| 3 | User with role <user_role> can run a Jupyter notebook from the applications tile using Accelerators with configuration <accelerator_config> | Golden Path |
| 4 | User can work in an Accelerated notebook (from a Workbench) | |
| 5 | User can work in an Accelerated notebook (from Jupyter Notebook tile) | |
| 6 | User can deploy a model in an Accelerated Model server | |
| 7 | Creating a Workbench using image <image_type> recommends using Accelerator <accelerator_type> | |
| 8 | Creating a Workbench using Accelerator <accelerator_type> recommends using image <image_type> | |
| 9 | Creating a Model Server using Serving Runtime <serving_runtime> recommends using Accelerator <accelerator_type> | |
| 10 | Creating a Model Server using Accelerator <accelerator_type> recommends using Serving Runtime <serving_runtime> | |
| 11 | When creating a model server, the user can flow between Accelerator values None -> <any_value> -> None | |
| 12 | Verify the existence of the Custom Resource Definition: Accelerator Profile | |
| 13 | Verify some of the values of the AcceleratorProfiles Instances | |
| 14 | Verify error when using an Accelerator with an identifier not detected in the cluster | |
| 15 | Edit a workbench modifying the Image and accelerator | |
| 16 | Edit a model server, modifying just the accelerator | |
| 17 | A tile Jupyter execution cannot be modified during runtime | |
| 18 | A user get a warning when exceeding the number of accelerators which is set by the HW configuration (Creating a workbench) | |
| 19 | A user get a warning when exceeding the number of accelerators which is set by the HW configuration (Creating a Model Server) | |
| 20 | A user get a warning when exceeding the number of accelerators which is set by the HW configuration (Launching a Jupyter Notebook from the Applications tile) | |
| 21 | A user get a warning when exceeding the number of accelerators which is set by the HW configuration (Editing a workbench) | |
| 22 | A user get a warning when exceeding the number of accelerators which is set by the HW configuration (Editing a Model Server) | |
| 23 | Deleting the Accelerator profile CRD makes Accelerator options disappear when creating a new Workbench | |
| 24 | Deleting the Accelerator profile CRD makes Accelerator options disappear when creating a new Model Server | |
| 25 | Deleting the Accelerator profile CRD makes Accelerator options disappear when launching a new Jupyter Notebook from Applications Tile | |
| 26 | Deleting the Accelerator profile CRD makes Accelerator options disappear when editing a running Workbench | |
| 27 | Deleting the Accelerator profile CRD makes Accelerator options disappear when editing a model server | |
| 28 | Deleting the Accelerator profile CRD and try to edit a workbench or a model server with Accelerator configuration. | |
| 29 | Disable an Accelerator (enabled = false) before an execution and the option would not show. | |
| 30 | Disable an Accelerator and try to edit an execution which was using it and the user get a "disabled" message in the dropdown | |
| 31 | Migration - Upgrade Cluster which was not using GPUs Before | |
| 32 | Migration - Upgrade Cluster which was using NVidia GPUs Before, but no resources were in use | |
| 33 | Migration - Upgrade Cluster which was using NVidia GPUs Before in a Workbench | |
| 34 | Migration - Upgrade Cluster which was using NVidia GPUs Before in a modelserver | |
| 35 | Migration - Upgrade Cluster which was using NVidia GPUs Before in a Jupyter Tile | |
| 36 | Migration - Upgrade Cluster which was using non NVidia GPUs Before | |
| 37 | Testing in operator V1 and V2 [WIP] |