ONAP Projects dealing with GUI must provide GUI test suites

Description of Use Case / Requirement:

UI testing is not trivial. Some components are providing UI (Portal, SDC, VID,...) that are the entry points for the end users so very important to give trust evidence for end users. As we started setting up gating and CI daily chain, it would be great to include UI testing for the main components as part of the regression test suites integrated in the CI chains

Proposal implementation :

Mandatory GUI-Tests have to be provided to verify:

• Standalone GUI startup without failures
• User Login (if applicable)
• GUI startup within Portal (if applicable)
  o For each user role

Addon Tests:

• Page functionality (e.g. dialog, search,…)
• Complete GUI workflow execution
• GUI accessibility test
• Internationalization

The tests have to run without any user interaction and have to be integratable into the Integration CI chains.
Existing frameworks (e.g. robot testsuite) include the Selenium test framework and might be an option to be used.

Tests should only use 'externally accessible UIs and tools', this means for example that to reach SDC UI, it needs to 'cross' Portal UI very much like a user would do.

Owners (one of these should be the Assignee - use @ notation):

Link to HLD/LLD (if any):

Dependency Relationships with Other Projects:

Project (ONAP Component #1) Portal

• Impact Type: Test Code to be provided to integration to verify GUI provided by the Portal team in CI chains
• Company Engagement: xyz
• Resources: xyz (People)
• Support Status: S/P/N (Supported/Partially supported/Not supported)

Project (ONAP Component #2) SDC

• Impact Type: Test Code to be provided to integration to verify GUI provided by the SDC team in CI chains
• Company Engagement: xyz
• Resources: xyz (People)
• Support Status: S/P/N (Supported/Partially supported/Not supported)

Project (ONAP Component #3) VID

• Impact Type: Test Code to be provided to integration to verify GUI provided by the VID team in CI chains
• Company Engagement: xyz
• Resources: xyz (People)
• Support Status: S/P/N (Supported/Partially supported/Not supported)

Integration Leads (use @ notation): 

mrichomme