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

Add integration tests #14

Merged
merged 1 commit into from
Mar 18, 2020
Merged

Add integration tests #14

merged 1 commit into from
Mar 18, 2020

Conversation

dtuite
Copy link
Member

@dtuite dtuite commented Mar 18, 2020

This is a low functionality proof of concept. It uses GitHub actions to do the following:

  1. Create a KinD k8s cluster in the Ubuntu box
  2. Runs kubewise with go run main.go
  3. Installs and uninstalls the zookeeper helm package.
  4. Uploads the logs somewhere.

There is lots of scope for improvement

  1. Assert that the output which is sent to Slack is correct. Currently, a manual visual inspection is required and I'm the only person who can see the Slack channel.
  2. Perform an upgrade in the tests. Currently I'm just doing install and uninstall.

Lower priority improvements

  1. Come up with a better way to background kubewise while giving it enough time to initialize before moving on with the helm commands. Currently I'm just using a sleep.
  2. Make more build variables. For example, the helm package, repo and version to install could be variables.
  3. Test the helm chart somehow. By using go run main.go I'm bypassing any problems which might happen in the chart.

@dtuite dtuite added the pipeline Relating to the build pipeline or releases. label Mar 18, 2020
@dtuite dtuite self-assigned this Mar 18, 2020
This is a low functionality proof of concept. It uses GitHub actions to do the following:

 1. Create a KinD k8s cluster in the Ubuntu box
 2. Runs kubewise with go run main.go
 3. Installs and uninstalls the zookeeper helm package.
 4. Saves the logs from KubeWise.

The idea is that the messages can be viewed in Slack and asserted for
correctness.

This isn't a nice solution and needs a lot more work. I need to learn
more about Go testing to figure out the best way to assert the output.
@dtuite dtuite force-pushed the integration-tests branch from b41179a to b4be96b Compare March 18, 2020 22:36
@dtuite dtuite merged commit 76d117c into master Mar 18, 2020
@dtuite dtuite deleted the integration-tests branch March 18, 2020 22:48
@dtuite dtuite linked an issue Mar 18, 2020 that may be closed by this pull request
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
pipeline Relating to the build pipeline or releases.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Automated testing
1 participant