-
Notifications
You must be signed in to change notification settings - Fork 115
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
Support running tests against Windows artifact #321
Comments
synced up with @peterzhuamazon The execution of the artifact and the test could all happen in the windows server. There won't be Docker for Windows. Peter will check into the Cypress support in Windows next week. |
Ideally, functional test should has dependencies on Browser, but not OS. what does it mean browser test should run browser test on test agent only required for test in order to support that, we need to build test infrastructure which could launch test environment only required to run browser test. unless we are going to certify cross browser and cross OS support (which is only important, but different priority), the test infra should not be blocked by support new OS(hosting environment) |
I was thinking about running Windows artifact on Windows and then exposing the endpoint. Then the tests can still run in a Linux env. However, this may require a remote endpoint. Running the artifact and the tests together in the Windows env is more convenient to avoid the remote endpoint. The cost is that we need to have Cypress installed in Windows. |
Verified we can directly install cypress on windows through npm.
The installed version, unlike arm64, is native. |
Next step:
|
More development and issues in here: |
Inspired by opensearch-project/opensearch-plugins#95 , create an issue to support running tests against Windows artifact.
The text was updated successfully, but these errors were encountered: