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.

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

chore: Build a jest based integration test to ensure that a provisioner works #206

Open
7 tasks
nsainaney opened this issue Feb 10, 2021 · 0 comments
Open
7 tasks
Labels

Comments

@nsainaney
Copy link
Contributor

nsainaney commented Feb 10, 2021

Background:

As our library grows, we are going to need to have automated tests for our provisioners. This task is to prove that it can be done.

Requirements:

  • Brush up on how jest unit tests work
  • Manually set up a k8s cluster and set KUBECONFIG to point to the config file. Alternatively, the jest test can assume that a test-kubeconfig.yaml is at a predefined location.

The test itself will:

  • The test will call provisionerManager.perform(appResource, 'create', answers) so the test can run silently
  • Use kubeclient to wait for certain components (pods, services etc) to be created
  • Time out after a configurable amount of time (jest has built in timeouts)
  • Call provisionerManager.perform(appResource, 'remove', answers) to uninstall the app
  • Check that resources are removed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants