-
Notifications
You must be signed in to change notification settings - Fork 284
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 dashboards functional test repo into build process #784
Conversation
Signed-off-by: Tianle Huang <[email protected]>
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.
Can you please revert Pipfile.lock
? That atomicwrites change is needed on Windows, but it's a Windows-only dependency. I added it explicitly in #786
Why add the tests into the build/bundle process? My concern is that it could add unrelated dependencies to the release build. Since these tests are in separate repo it it might be easier to add a stage during test execution to pull them in. If we did want to build test at the same time, I'd recommend updating the manifest schema to treat them distinctly. |
We might need an updated ci check and way to make sure that platform specific dependencies are not getting axed accidentally |
Good point, we just need to run tests if Pipfile or Pipfile.lock have changed. I updated #786 |
Signed-off-by: Tianle Huang <[email protected]>
Thanks for calling out. Reverted. |
Description
As part of the ongoing effort to support dashboards functional tests, #604, we want to add this repo https://github.com/opensearch-project/opensearch-dashboards-functional-test into the build process. Note that this repo contains only test cases and is not a regular dashboards plugin. Thus we only have an empty build script for it.
Issues Resolved
#783
Test
Verified that manifest yml
Check List
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.