Dashboard readiness - Dashboard Testcase:

• Verify Tile {{ CUSTOM_NAME }}

• Verity Tile can launch app
  

Luca's suggestion:  Have 2 parameters in the test cases    (tile name, tab name, menu name)

Important info from the epic RHODS-142:

• Epic brief with requirements: Dashboard Access To Services
• Requirements:

1. P0: The system must enable users to view all available services (not already installed). This includes the following partner applications: Anaconda, Starburst, Seldon, IBM Watson Studio, Pachyderm (TBD), Intel OpenVino. This also includes the following RH services: RHOSAK, RHOAM.
2. P0: The system must provide a method for accessing all installed/subscribed to services from a central page/dashboard. This includes all supported partner and RH services listed in req 1. 
3. P1: The system must allow users to access any installed service without any additional login process. This assumes the user is already logged in to MODH.
4. P1: The system must provide options for users to search for available services. 
5. P0: The system must enable users to differentiate between installed services and available but not installed services.
6. P0: The system must enable users to initiate a flow to purchase any available services.
7. P1: The system must provide the ability to view all documentation for a single product/vendor. 
8. P1: The system must enable users to view doc only for 'enabled' services.
9. P0: The system must enable users to access endpoint information for any installed services.

Types of services (taken from RHODS-347):

1) SaaS (partner-managed): we currently have no way to know whether it should be enabled or not

2) Self-managed (operator software): we can enable via the operator CR name on the cluster

3) Managed-service addons: That should be pretty similar to the operator model as #2 ... the only thing is the operator CR will get created after an addon is installed

Related documents:

• RHODS ISV Application Definition