Is your feature request related to a problem?
need for a consensus approach for opensearch-dashboard repository to use the opensearch-dashboards-test-library
What solution would you like?
opensearch-dashboard team prefers to consume the test library as a published npm package, like other dependent packages it currently uses.
we need to establish a standard process for npm package publish, currently it is tribe knowledge.
What alternatives have you considered?
Instead of consume the test library as a publish npm version. opensearch-dashboard can also directly use it by branch reference, like how the opensearch-dashboards-functional-test repo imports it now: https://github.com/opensearch-project/opensearch-dashboards-functional-test/blob/main/package.json#L39
Trade-off comparison?
Publishing a version npm packages allows us to have version control. And avoid introducing breaking changes from test library to consuming repositories.
Using the branch reference approach saves us from conducting npm package publish process on test library, and package upgrade on consuming repositories. But it requires the change on test library must be backward compatible, otherwise this may lead to breaking changes or regression on client repositories. Increased development and test difficulty.
Do you have any additional context?
related issues:
opensearch-project/opensearch-dashboards-functional-test#29
Is your feature request related to a problem?
need for a consensus approach for opensearch-dashboard repository to use the opensearch-dashboards-test-library
What solution would you like?
opensearch-dashboard team prefers to consume the test library as a published npm package, like other dependent packages it currently uses.
we need to establish a standard process for npm package publish, currently it is tribe knowledge.
What alternatives have you considered?
Instead of consume the test library as a publish npm version. opensearch-dashboard can also directly use it by branch reference, like how the opensearch-dashboards-functional-test repo imports it now: https://github.com/opensearch-project/opensearch-dashboards-functional-test/blob/main/package.json#L39
Trade-off comparison?
Publishing a version npm packages allows us to have version control. And avoid introducing breaking changes from test library to consuming repositories.
Using the branch reference approach saves us from conducting npm package publish process on test library, and package upgrade on consuming repositories. But it requires the change on test library must be backward compatible, otherwise this may lead to breaking changes or regression on client repositories. Increased development and test difficulty.
Do you have any additional context?
related issues:
opensearch-project/opensearch-dashboards-functional-test#29