Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Improve Testing #2

Open
edenreich opened this issue Aug 20, 2024 · 0 comments
Open

Improve Testing #2

edenreich opened this issue Aug 20, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@edenreich
Copy link
Owner

edenreich commented Aug 20, 2024 •
edited
Loading

Summary

Currently some tests are broken, those tests are End to End tests which can take pretty long time to execute, but on the same time they give an accurate indication about the behaviour of the system.

The sequence or the way they are currently working is:

  • A local K8S cluster is being created using k3d.
  • A dummy API (external system) is being created from the OAS.
  • The operator is being deployed.
  • Some CRD are being deployed.
  • Verification of the CRD object created in the cluster.
  • Verification of Meta Data and CRD's status.

As a maintainer of this project I want to make it as easy as possible for the consumer to test their operator behaviour by providing abstracted functions they can call to validate.

After those tests are solid enough I could probably just generate them from the OAS.
@edenreich edenreich added the enhancement New feature or request label Aug 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@edenreich