-
Notifications
You must be signed in to change notification settings - Fork 152
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
E2E tests not running on Ubuntu/WSL #853
Comments
Tried solving this but looks like WSL needs a lot of work to get graphical chromium working and our puppeteer wont work until we do that. Since, we have |
This issue has been marked as being beyond the support scope of Accessibility Insights. It will now be closed automatically for house-keeping purposes. |
After some investigation and solving this problem on our PR/CI builds; a solution to this problem is to use the commands that we use in Docker file mentioned in docker file. So, basically use the following commands: sudo apt-get update sudo apt-get install -yq gconf-service libasound2 libatk1.0-0 libc6 libcairo2 libcups2 libdbus-1-3 libexpat1 libfontconfig1 libgcc1 libgconf-2-4 libgdk-pixbuf2.0-0 libglib2.0-0 libgtk-3-0 libnspr4 libpango-1.0-0 libpangocairo-1.0-0 libstdc++6 libx11-6 libx11-xcb1 libxcb1 libxcomposite1 libxcursor1 libxdamage1 libxext6 libxfixes3 libxi6 libxrandr2 libxrender1 libxss1 libxtst6 ca-certificates fonts-liberation libappindicator1 libnss3 lsb-release xdg-utils wget x11vnc x11-xkb-utils xfonts-100dpi xfonts-75dpi xfonts-scalable xfonts-cyrillic x11-apps xvfb
yarn install --frozen-lockfile yarn build:dev xvfb-run --server-args=\"-screen 0 1024x768x24\" yarn test:e2e |
Describe the bug
e2e tests are not being able to run on ubuntu wsl.
To Reproduce
Steps to reproduce the behavior:
yarn build
yarn test:e2e
Expected behavior
e2e test cases should work
Screenshots
Extension (please complete the following information)
Are you willing to submit a PR?
Yes
Did you search for similar existing issues?
Yes
Additional context
The text was updated successfully, but these errors were encountered: