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

tests: Add better test coverage for nodejs SDK #124

Closed
3 tasks done
metral opened this issue May 3, 2019 · 1 comment
Closed
3 tasks done

tests: Add better test coverage for nodejs SDK #124

metral opened this issue May 3, 2019 · 1 comment
Assignees
Milestone

Comments

@metral
Copy link
Contributor

metral commented May 3, 2019

Currently we have the following nodejs examples/tests:

We should also be testing commits against the following use-cases:

Note: To verify the k8s cluster "remains in a running state," a small scoped smoke-test testing the following would suffice:

  • The aws-auth k8s ConfigMap can be retrieved, is correct, and can be correctly used by Nodes to join the cluster with no interruptions.
  • All existing k8s nodes remain RUNNING
  • All existing k8s pods remain RUNNING
@metral
Copy link
Contributor Author

metral commented Mar 20, 2020

Closing as this has been complete for a while, and our smoke tests validate all pods scheduled are in the RUNNING or SUCCEEDED state.

@metral metral closed this as completed Mar 20, 2020
@metral metral added this to the 0.33 milestone Mar 20, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants