Skip to content
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

Closed
Shobhit1 opened this issue Jun 25, 2019 · 4 comments · Fixed by #856
Closed

E2E tests not running on Ubuntu/WSL #853

Shobhit1 opened this issue Jun 25, 2019 · 4 comments · Fixed by #856
Labels
bug Something isn't working category: engineering resolution: out of scope This issue has been identified as out of scope for this project.

Comments

@Shobhit1
Copy link
Contributor

Shobhit1 commented Jun 25, 2019

Describe the bug

e2e tests are not being able to run on ubuntu wsl.

To Reproduce
Steps to reproduce the behavior:

  1. Clone the latest code
  2. run yarn build
  3. run yarn test:e2e
  4. See error

Expected behavior

e2e test cases should work

Screenshots

image

Extension (please complete the following information)

  • OS: Windows 10/ WSL (ubuntu)
  • Version: Dev

Are you willing to submit a PR?

Yes

Did you search for similar existing issues?

Yes

Additional context

@Shobhit1 Shobhit1 added the bug Something isn't working label Jun 25, 2019
@msft-github-bot msft-github-bot added the status: new This issue is new and requires triage by DRI. label Jun 25, 2019
@DaveTryon DaveTryon added status: active This issue is currently being worked on by someone. and removed status: new This issue is new and requires triage by DRI. labels Jun 25, 2019
@DaveTryon DaveTryon assigned Shobhit1 and unassigned DaveTryon Jun 25, 2019
@Shobhit1
Copy link
Contributor Author

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 headless: false as a setting. Closing this issue and will create a Readme note for this.

@Shobhit1 Shobhit1 reopened this Jun 25, 2019
@Shobhit1 Shobhit1 added category: engineering resolution: out of scope This issue has been identified as out of scope for this project. and removed status: active This issue is currently being worked on by someone. labels Jun 25, 2019
@msft-github-bot
Copy link
Collaborator

This issue has been marked as being beyond the support scope of Accessibility Insights. It will now be closed automatically for house-keeping purposes.

@Shobhit1
Copy link
Contributor Author

Shobhit1 commented Jul 11, 2019

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working category: engineering resolution: out of scope This issue has been identified as out of scope for this project.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants