Skip to content
This repository has been archived by the owner on Oct 22, 2021. It is now read-only.

Add basic dev guide about how to run tests #39

Closed
wants to merge 1 commit into from
Closed

Add basic dev guide about how to run tests #39

wants to merge 1 commit into from

Conversation

peterhaochen47
Copy link
Member

Just what we can think of so far. Please correct/edit/add to the draft as you see fit!

@mudler
Copy link
Member

mudler commented Aug 21, 2020

Thanks for your contribution! We are moving all the documentation bits to its own repo https://github.com/cloudfoundry-incubator/quarks-docs - do you feel opening the PR there? we already have https://quarks.suse.dev/docs/development/testing/#tests-description but sadly isn't updated to reflect latest changes

onto a running k8s cluster and apply the QuarksSecret examples included in the [/docs/examples](/docs/examples) directory.
* Pre-requisites:
* A locally running k8s cluster accessible via `kubectl` (same as the integration tests).
* Edit the values in the [helm chart values file](/deploy/helm/quarks-secret/values.yaml)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This shouldn't be needed, we have the bin/test-helm-e2e helper which should be taking care of this

@peterhaochen47
Copy link
Member Author

@mudler I'm reading the related slack thread about this. It seems like there's more restructuring to be done in the main dev guide repo? In that case, I'll leave that to you all who are more familiar with all the components then.

We opened this PR because we didn't know how to run tests and couldn't find any docs. But if you all already have plans to add docs then it's fine!

@manno
Copy link
Member

manno commented Aug 24, 2020

Let me leave the doc site url here: https://quarks.suse.dev/
It has lots of notes

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants