-
Notifications
You must be signed in to change notification settings - Fork 61
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
Added Tests for the test framework #310
Conversation
Changes AnalysisCommit SHA: 59c2064 API ChangesSummaryNO CHANGES ReportThe full API changes report is available at: https://github.com/opensearch-project/opensearch-api-specification/actions/runs/9372884295/artifacts/1568212464 API Coverage
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good. Fix CI, + some minor things.
I do recommend putting back the empty.yaml as a a minimal test of passing something that has no actual tests in it.
tools/tests/tester/helpers.ts
Outdated
// The password must match the one specified in .github/workflows/test-spec.yml | ||
process.env.OPENSEARCH_PASSWORD = 'myStrongPassword123!' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why are we hard coding a password here, this should just be set in the workflow
// The password must match the one specified in .github/workflows/test-spec.yml | ||
process.env.OPENSEARCH_PASSWORD = 'myStrongPassword123!' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why are we hard coding a password here, this should just be set in the workflow
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I should change it to
process.env.OPENSEARCH_PASSWORD = process.env.OPENSEARCH_PASSWORD ?? 'myStrongPassword123!'`
The idea is streamlining local testing for the user. When they run docker compose up
, this is the same password the cluster will be setup with by default. So, they can quickly run the tests right after the contain is set up and ready.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's not a security concern since this is just for testing and the password is already shown in the workflow.
5e7b3ab
to
7f050f5
Compare
Figuring out why the tests fail here but not locally. Changing this to draft. Please ignore the commit pushes till I change it back to reviewable. |
@dblock We currently does not allow an empty story because the |
Signed-off-by: Theo Truong <[email protected]>
022b7dd
to
59c2064
Compare
It's ready for review now |
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.