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

Integration testing strategy #5

Open
zpratt opened this issue Feb 2, 2020 · 4 comments
Open

Integration testing strategy #5

zpratt opened this issue Feb 2, 2020 · 4 comments
Labels
idea I had an idea.. Uh oh

Comments

@zpratt
Copy link
Owner

zpratt commented Feb 2, 2020

Step 1: use helm tests
Step 2: if, for some reason, these become unwieldy, then consider adopting octopus

@zpratt
Copy link
Owner Author

zpratt commented Feb 2, 2020

A job within the context of a helm test should be able to trigger cucumber.js tests, in theory.

Possibly useful example of wiring things together: https://github.com/zpratt/react-cucumber-js

@zpratt
Copy link
Owner Author

zpratt commented Feb 2, 2020

I plan to first rely on integration tests instead of unit tests just to see how this goes. If I feel the design of the application suffers from a lack of TDD, then I'll stop being lazy and use a TDD approach in addition to integration tests.

@zpratt zpratt added the idea I had an idea.. Uh oh label Feb 2, 2020
@zpratt
Copy link
Owner Author

zpratt commented Aug 10, 2020

Personal note for this sweet usage of test containers: https://github.com/profefe/kube-profefe/blob/master/pkg/profefe/client_test.go

Note: this project has several examples of tests using the fake client-go library.

@zpratt
Copy link
Owner Author

zpratt commented Dec 29, 2021

Going to start with terratest first after reading this

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
idea I had an idea.. Uh oh
Projects
None yet
Development

No branches or pull requests

1 participant