liquidmetal-dev / liquidmetal-dev/cluster-api-provider-microvm

Update the e2es to run against latest versions

Open
#268 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

kind/test
Dominant language
Go
Stars
157
Forks
21
PR merge metrics
No merged PRs in 30d

Description

Using the CAPI test framework means you need to copy manifests and metadata over to the test location. Or hopefully I am wrong and you don't because that is rubbish.

In either case, the tests are using artefacts that I copied over months ago (stuff in [here](https://github.com/weaveworks-liquidmetal/cluster-api-provider-microvm/tree/main/test/e2e/data/infrastructure-microvm) and [here](https://github.com/weaveworks-liquidmetal/cluster-api-provider-microvm/blob/main/test/e2e/data/v1beta1_provider/metadata.yaml) and probably others that I have forgotten). Let's have some automation in place which updates this data as part of a new release or whatever.

[This stuff](https://github.com/weaveworks-liquidmetal/cluster-api-provider-microvm/blob/main/test/e2e/config/e2e_conf.yaml) could also do with an update to probably.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by inspecting test/e2e/data/infrastructure-microvm, test/e2e/data/v1beta1_provider/metadata.yaml, and test/e2e/config/e2e_conf.yaml to understand which copied artifacts the CAPI tests use. Determine how releases are produced and how the e2e suite consumes this data; done means a release or equivalent automation refreshes the artifacts and the configuration and e2e tests use current versions.

Written by the indexing model from the issue text.

Assessment

Tech stack
go, kubernetes, yaml
Domain
build-system, release, testing
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.