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

Test sample app in CI #165

Merged
merged 1 commit into from
Aug 23, 2022
Merged

Test sample app in CI #165

merged 1 commit into from
Aug 23, 2022

Conversation

scothis
Copy link
Contributor

@scothis scothis commented Aug 20, 2022

In addition to the conformance test suite, we should also start to test
our samples. This change updates the spring-petclinic sample to use kapp
to deploy and updates the sample readme to describe the benefits of kapp
and how we leverage them for the sample.

Signed-off-by: Scott Andrews andrewssc@vmware.com

In addition to the conformance test suite, we should also start to test
our samples. This change updates the spring-petclinic sample to use kapp
to deploy and updates the sample readme to describe the benefits of kapp
and how we leverage them for the sample.

Signed-off-by: Scott Andrews <andrewssc@vmware.com>
@scothis scothis marked this pull request as ready for review August 20, 2022 15:04
@scothis scothis requested review from baijum, sadlerap and a team August 20, 2022 15:05
Comment on lines +302 to +311
- name: Test samples
run: |
set -o errexit
set -o nounset
set -o pipefail

echo "##[group]Deploy spring-petclinic"
${KAPP} deploy -a servicebinding-sample-spring-petclinic -n apps --wait-timeout 5m -y \
-f samples/spring-petclinic
echo "##[endgroup]"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Q: Does it make sense to have these in the same run pipeline as conformance tests? If these break, I don't want them to gate running conformance tests (or vice-versa, for that matter).

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

it's running in the acceptance job. I view conformance as one part of acceptance for the RI. If there's a change that breaks a basic e2e app, we know the change isn't going to pass conformant (I hope). If you prefer, I can move this after the conformance tests.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I was hoping to have a little more granularity in tests here. For now, it'll probably be fine (since we're still trying to get out of bootstrapping testing), but long-term I'd prefer to have separate pipeline stages for separate test suites.

@scothis scothis merged commit 02c1bfd into servicebinding:main Aug 23, 2022
@scothis scothis deleted the test-sample branch August 23, 2022 16:52
sadlerap pushed a commit to sadlerap/service-binding-runtime that referenced this pull request Aug 24, 2022
In addition to the conformance test suite, we should also start to test
our samples. This change updates the spring-petclinic sample to use kapp
to deploy and updates the sample readme to describe the benefits of kapp
and how we leverage them for the sample.

Signed-off-by: Scott Andrews <andrewssc@vmware.com>
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.

3 participants