Alexandre Alves
Alexandre Alves
Added possible `automation-candidate` IF we can mock the requests needed in order to load the machine-config for an Azure RKE2 cluster and check if default region is set. We might...
Added `automation-candidate` based on https://github.com/rancher/dashboard/blob/master/cypress/e2e/tests/pages/manager/cluster-provisioning-azure-rke2.spec.ts#L41-L66
For e2e, just check if correct payload is being sent to the backend. As per indicated by @nwmac on sprint planning that would suffice in terms of testing from the...
working on e2e automation at the moment
@yonasberhe23 @IsaSih @izaac added an e2e test for this issue https://github.com/rancher/dashboard/pull/10918. it's merged
@lindhe this is fixed with https://github.com/rancher/dashboard/pull/9803. Fix "will be available to the public" once we release Rancher `2.9`. The other PR I added was just an e2e test to cover...
@nwmac do we need to update JIRA (`SURE-5789`) about this issue? Is it blocked by backend?
For an e2e, one could use https://github.com/rancher/dashboard/pull/10898 as a basis
Added as possible `automation-candidate`. Login part could probably be tested with a unit test... Settings page we have several e2e that we could piggy-back on.
Based on https://github.com/rancher/dashboard/blob/master/cypress/e2e/blueprints/nav/fake-cluster.ts, if the `Daemonsets` are browsable, we might be able to test this on an e2e. Possible `automation-candidate`