Notebooks 2.0 // Frontend // Add test-and-build check to GitHub actions

[jenny-s51]

Per our discussions regarding the a11y fixes in kubeflow/model-registry#596 and the existing violations that were raised in kubeflow/dashboard#64.

Following the existing infrastructure in Model Registry, we want to continue upholding and maintaining a11y standards and detect any violations in our CI checks throughout the Notebooks 2.0 effort.

• Add a test-and-build check as done in https://github.com/ederign/model-registry/blob/main/.github/workflows/ui-frontend-build.yml
• Set up Cypress UI testing to detect any a11y violations in the frontend.

cc @ederign @paulovmr

[ederign]

/assign @paulovmr

[google-oss-prow]

@ederign: GitHub didn't allow me to assign the following users: paulovmr.

Note that only kubeflow members with read permissions, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time.
For more information please see the contributor guide

In response to this:

/assign @paulovmr

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[ederign]

Thank you so much @jenny-s51!

[paulovmr]

Commenting so I can be assigned :)

[ederign]

/assign @paulovmr