E2E tests - run the tests suite on new PRs

[torchiaf]

Contributes to #71

This covers point 1. of the issue, by adding the e2e tests suite to test the extension in dev mode.

• Implement mock Agent to replace the real Agent and LLM during tests
• Implement the UI assistant e2e tests
• Add commands to control the mock Agent messages - see cy.enqueueAIAgentResponse
• commit ad16791 is a porting of rancher/dashboard cypress framework, excluding the tests folder.

[rak-phillip]

I think that this looks good. I tried to rule out the imported POs and to focus on functionality. For the future, do we need to consider how we will keep cypress POs & commands in sync with Dashboard?

I'm able to run the tests, but the first fails with the following error:

  Rancher setup
    (Attempt 1 of 3) First login & Configure
    (Attempt 2 of 3) First login & Configure
    1) First login & Configure
cypress-terminal-report: Wrote html logs to /home/phillip/Development/rancher-ai-ui/browser-logs/out.html. (1ms)


  0 passing (4s)
  1 failing

  1) Rancher setup
       First login & Configure:
     CypressError: `cy.type()` cannot accept an empty string. You need to actually type something.

https://on.cypress.io/type
      at Context.type (https://localhost:8005/__cypress/runner/cypress_runner.js:137615:76)
      at wrapped (https://localhost:8005/__cypress/runner/cypress_runner.js:157819:19)
  From Your Spec Code:
      at ./cypress/e2e/po/components/password.po.ts.PasswordPo.set (webpack:///./cypress/e2e/po/components/password.po.ts:35:0)
      at ./cypress/e2e/po/pages/rancher-setup-login.po.ts.RancherSetupLoginPagePo.bootstrapLogin (webpack:///./cypress/e2e/po/pages/rancher-setup-login.po.ts:39:0)
      at Context.eval (webpack:///./cypress/e2e/tests/rancher-setup.spec.ts:17:0)




  (Results)

  ┌────────────────────────────────────────────────────────────────────────────────────────────────┐
  │ Tests:        1                                                                                │
  │ Passing:      0                                                                                │
  │ Failing:      1                                                                                │
  │ Pending:      0                                                                                │
  │ Skipped:      0                                                                                │
  │ Screenshots:  3                                                                                │
  │ Video:        true                                                                             │
  │ Duration:     3 seconds                                                                        │
  │ Spec Ran:     rancher-setup.spec.ts                                                            │
  └────────────────────────────────────────────────────────────────────────────────────────────────┘

[rak-phillip]

I think we're missing a step. This doesn't launch the cypress dashboard, it starts the dev server. I think we need a line for ➤ TEST_PASSWORD=${ rancher-password } yarn e2e.

[torchiaf]

Fixed, thanks.

[torchiaf]

For the future, do we need to consider how we will keep cypress POs & commands in sync with Dashboard?

Definetely, this can also be useful for other extensions.
I'll add an additional point to #71, in theory it should be possible to publish the POs and commands as NPM package.

[torchiaf]

I'm able to run the tests, but the first fails with the following error:

@rak-phillip TEST_SKIP=setup usage was wrong and not handled in cypress.config.ts.
The rancher-setup.spec.ts is meant to setup the rancher password and accept the Terms&Conditions at first login.
It's now being excluded when you run tests locally with the TEST_SKIP=setup active.

I also added a new e2e to test the sliding badges.