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 smoke tests to the test manifest schema #5127

Merged
merged 3 commits into from
Oct 31, 2024

Conversation

zelinh
Copy link
Member

@zelinh zelinh commented Oct 22, 2024

Description

Add smoke tests to the test manifest schema

Issues Resolved

#5126

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

@@ -36,6 +36,9 @@ class TestManifest(ComponentManifest['TestManifest', 'TestComponents']):
test-configs:
- with-security
- without-security
smoke-test:
test-spec:
Copy link
Member

Choose a reason for hiding this comment

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

Do we want to keep this as test-configs? Similar to integ-test and bwc test?

Copy link
Member Author

Choose a reason for hiding this comment

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

I'm thinking it's not technically config? Keep it as test-configs may cause some confusion to users since we don't modify any of the cluster configuration.

"smoke-test": {
"type": "dict",
"schema": {
"test-spec": {"type": "list"},
Copy link
Member

Choose a reason for hiding this comment

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

Do we need to use list here? More than 1 spec file for each test?

Copy link
Member

@gaiksaya gaiksaya left a comment

Choose a reason for hiding this comment

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

We can start with one spec per component and then iterate if we need more. Would recommend to add multiple specs under same file rather than having multiple spec files for one component.

@zelinh
Copy link
Member Author

zelinh commented Oct 30, 2024

We can start with one spec per component and then iterate if we need more. Would recommend to add multiple specs under same file rather than having multiple spec files for one component.

Sure let me update it to a single string of spec for now. We can enhance later if we really need more. Thanks.

Signed-off-by: Zelin Hao <[email protected]>
@@ -37,8 +37,7 @@ class TestManifest(ComponentManifest['TestManifest', 'TestComponents']):
- with-security
- without-security
smoke-test:
test-spec:
- spec.yaml
test-spec: spec.yaml
Copy link
Member

@peterzhuamazon peterzhuamazon Oct 31, 2024

Choose a reason for hiding this comment

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

Can we keep it consistent here?
.yaml or .yml?

Thanks.

Copy link
Member Author

Choose a reason for hiding this comment

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

Sure updated to .yml.

Signed-off-by: Zelin Hao <[email protected]>
@zelinh
Copy link
Member Author

zelinh commented Oct 31, 2024

@gaiksaya @peterzhuamazon Any final thoughts or concerns before we merge this PR?

@peterzhuamazon
Copy link
Member

peterzhuamazon commented Oct 31, 2024

@gaiksaya @peterzhuamazon Any final thoughts or concerns before we merge this PR?

LGTM, thanks.

@zelinh zelinh merged commit c56153c into opensearch-project:main Oct 31, 2024
10 checks passed
@zelinh zelinh deleted the add-smoke-test-schema branch October 31, 2024 21:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: ✅ Done
Development

Successfully merging this pull request may close these issues.

3 participants