This story and its sub-tasks are self descriptive plan around integration new UI automation tool. This tool should serve as an improvement for quality engineering in Service Mesh team. Also story is providing more visibility, time/schedule and inclusive decisions for all teams participated.

So far, effort to integrate Cypress was tracked in Github PR's here and here . These were overall positively commented, but did not get merged for specific reasons. Putting upstream effort and reasons aside, we still need to address pain points when testing downstream.

Acceptance criteria:

• merge cypress into kiali/kiali-ui repository 
• start using it on daily basis (locally is fine)
• reduce manual testing backlog - automate manual test cases (few is fine)
• migrate few test-cases form current selenium UI suite to have PoC on supplying its functionality ( currently we have hard-to-maintain test cases in selenium, time well spent will be refactor and rewrite them in to cypress)
• have docs / example how to add suite into CI/CD 

Nice to have (not this story?):

• rock solid and repeatable results 
• CI/CD integration (for now we are happy with running locally)
• recording of failed test cases