-
Notifications
You must be signed in to change notification settings - Fork 960
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
[Docs] Update functional testing instructions #2462
Comments
For "All other tests will be", currently there is no concrete plan for it. The team could gradually build the development velocity by migrating a few tests first. We also welcome the community to help. We have some high level proposal to automate test generation opensearch-project/opensearch-dashboards-functional-test#205 which could extend to automate migration test cases from Selenium to Cypress. This may require some research. |
Created #2491 to collect feedback and track the migration plan. |
Updates the Readme to call out the change in functional testing for OpenSearch Dashboards Issue resolved: #2462 Signed-off-by: Ashwin P Chandran <ashwinpc@amazon.com>
Updates the Readme to call out the change in functional testing for OpenSearch Dashboards Issue resolved: opensearch-project#2462 Signed-off-by: Ashwin P Chandran <ashwinpc@amazon.com> Signed-off-by: Sergey V. Osipov <sipopo@yandex.ru>
opensearch-dashboards-functional-test is the official home for OpenSearch Dashboards Functional tests. Since the migration of all the tasks is non trivial, the decision was to incrementally target the migration. To communicate this openly we should update the TESTING.md readme with clear instructions on migration plan and steps to write the new tests.
Migration plan:
The text was updated successfully, but these errors were encountered: