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

feat: make binary installable using go install #277

Closed
wants to merge 5 commits into from

Conversation

fredrikaverpil
Copy link
Member

  • feat: replace context field with a function
  • feat: replace service field with a function
  • feat: new way to bootstrap the tests
  • feat: make binary installable via go install
  • fix: broken link

thall and others added 5 commits October 4, 2024 09:09
This commit replaces the `ctx` field on the config struct,
with a function for getting a context.
Same context is used as before, this is preparation for
upcomming commits.
This commit replaces the `service` field on the config struct,
with a function for getting the service to be tested.
This is a preparation for upcomming commit.
### Why

We have noticed historically, that when people adds new
resources, it's easy to forget to implement the newly
generated AIP tests, either directly or later.

### How

This commit tries to solve that issue by introducing a
main entrypoint to execute the tests, which takes a interface
that the user needs to implement.

When a new resource is added, the interface will be extended with
another method that the user needs to implement, if not, a compilation
error would be raised.

The user can choose to return `nil` to indicate that it can't be
implemented right directly.

All tests will still be executed, but if not implemented it will be
skipped, this to show it's available but not implemented.

This commit is backwards compatible with the current test setup.

For example usage, see `examples/`.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants