regression: UI

[lanfon72]

This PR will cover all of UI regression test cases.
Changes:

• exclude all files under cypress/cypress, which automatically generated by cypress.
• explicitly check the header after cy.login()
• add new task readYaml for checking yaml content.
• add new tasks deleteFolder and deleteFile.
• remove partially implemented generate support bundle and doc comments
• implement test cases:
  1. Links of Community Section
  2. Download KubeConfig File
  3. Generate Support Bundle (by the limitation, it will only verify form's behavior)

Limitation:

• Unable to catch the generated support bundle file¹, the example² is not work for our dashboard.
• context be treated as describe, so there is no scope for sub-tests, every it will trigger before/beforeEach/after/afterEach. (thus, merge sub test cases of links into single test case)

Footnotes

1. https://github.com/cypress-io/cypress/issues/8619 ↩

2. https://github.com/cypress-io/cypress-example-recipes/blob/master/examples/testing-dom__download/cypress/integration/form-submission-spec.js ↩

[TachunLin]

LGTM. Verified and tested the new tetscases in support.spec running correctly.

[lanfon72]

I should update the Generate Support Bundle test case to be more clearly, please don't merge it before new commits.

After testing is done, there should not display the message as below:

[TachunLin]

Verified the new tasks and test cases running correctly
Also did not show error message after test complete

[noahgildersleeve]

@lanfon72 I added in a test case for downloading the support bundle. I think I got it working without a timeout triggering. I found a solution that involved running an event listener here. I added in comments in the code. Take a look when you get a chance and let me know if you have any questions or concerns. The solution is a little fragile, but I think it should probably work. The issue is that it has three overlapping timeouts that it balances between.

[lanfon72]

@noahgildersleeve, I had tried this solution, but I thought it is not fit our test case.
(we would need verify the Zipfile's content on demend)

After discuss with my frontend friend, I think this commit 335a5b0 should more fit our case.

[lanfon72]

The API not always be called, so I will not check it.

[lanfon72]

The last response will contains support bundle's filename

[irishgordo]

@lanfon72 - I'm wondering if this is something we can also scaffold on the backend for our tests.
I started to dig into it a bit here:
irishgordo@a6ac4be

I know for: harvester/harvester#2321 - the introduction of "fleet-agent-" and "fleet-controller-" as directories inside of "logs", that could be something we could check for since I believe the feature will be backported.

[lanfon72]

@irishgordo yeah it is good if API's test can cover it too.
We have only few test cases about support bundle, I think the PR is new test case that we need to cover.