-
Notifications
You must be signed in to change notification settings - Fork 116
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
Better e2e ci tests with CircleCI #165
Labels
Comments
sjelin
added a commit
to sjelin/webdriver-manager
that referenced
this issue
Nov 25, 2016
Travis only runs a subset of tests via `npm run test_travis`, but `npm test` runs a full suite. See angular#165 for details on why travis cannot run all tests.
Merged
sjelin
added a commit
to sjelin/webdriver-manager
that referenced
this issue
Nov 25, 2016
Travis only runs a subset of tests via `npm run test_travis`, but `npm test` runs a full suite. See angular#165 for details on why travis cannot run all tests.
sjelin
added a commit
to sjelin/webdriver-manager
that referenced
this issue
Nov 25, 2016
Travis only runs a subset of tests via `npm run test_travis`, but `npm test` runs a full suite. See angular#165 for details on why travis cannot run all tests.
sjelin
added a commit
to sjelin/webdriver-manager
that referenced
this issue
Nov 28, 2016
Travis only runs a subset of tests via `npm run test_travis`, but `npm test` runs a full suite. See angular#165 for details on why travis cannot run all tests.
sjelin
added a commit
to sjelin/webdriver-manager
that referenced
this issue
Nov 28, 2016
Travis only runs a subset of tests via `npm run test_travis`, but `npm test` runs a full suite. See angular#165 for details on why travis cannot run all tests.
sjelin
added a commit
to sjelin/webdriver-manager
that referenced
this issue
Nov 28, 2016
Travis only runs a subset of tests via `npm run test_travis`, but `npm test` runs a full suite. See angular#165 for details on why travis cannot run all tests.
sjelin
added a commit
that referenced
this issue
Nov 28, 2016
Travis only runs a subset of tests via `npm run test_travis`, but `npm test` runs a full suite. See #165 for details on why travis cannot run all tests.
sjelin
added a commit
to sjelin/webdriver-manager
that referenced
this issue
Dec 1, 2016
Sadly, x86 emulation is impossible (no hardware extensions on circle) and arm is unworkably slow, so no android tests. See angular#167 for ideas about work arounds Removed travis tests since circle tests are cooler anyway Made some timeouts longer because I guess circle is slow. Also improved some an error path in downloader because it was a problem while debugging. Sample output: https://circleci.com/gh/sjelin/webdriver-manager/31 Closes angular#165
Sadly, x86 emulation is impossible (no hardware extensions on circle) and arm is unworkably slow, so no android tests. See #167 for ideas about work arounds |
sjelin
added a commit
to sjelin/webdriver-manager
that referenced
this issue
Dec 16, 2016
Sadly, x86 emulation is impossible (no hardware extensions on circle) and arm is unworkably slow, so no android tests. See angular#167 for ideas about work arounds Removed travis tests since circle tests are cooler anyway Made some timeouts longer because I guess circle is slow. Also improved some an error path in downloader because it was a problem while debugging. Sample output: https://circleci.com/gh/sjelin/webdriver-manager/31 Closes angular#165
sjelin
added a commit
to sjelin/webdriver-manager
that referenced
this issue
Dec 16, 2016
Sadly, x86 emulation is impossible (no hardware extensions on circle) and arm is unworkably slow, so no android tests. See angular#167 for ideas about work arounds Removed travis tests since circle tests are cooler anyway Made some timeouts longer because I guess circle is slow. Also improved some an error path in downloader because it was a problem while debugging. Sample output: https://circleci.com/gh/sjelin/webdriver-manager/31 Closes angular#165
sjelin
added a commit
to sjelin/webdriver-manager
that referenced
this issue
Dec 16, 2016
Sadly, x86 emulation is impossible (no hardware extensions on circle) and arm is unworkably slow, so no android tests. See angular#167 for ideas about work arounds Removed travis tests since circle tests are cooler anyway Made some timeouts longer because I guess circle is slow. Also improved some an error path in downloader because it was a problem while debugging. Sample output: https://circleci.com/gh/sjelin/webdriver-manager/31 Closes angular#165
sjelin
added a commit
to sjelin/webdriver-manager
that referenced
this issue
Dec 16, 2016
Travis only runs a subset of tests via `npm run test_travis`, but `npm test` runs a full suite. See angular#165 for details on why travis cannot run all tests.
sjelin
added a commit
to sjelin/webdriver-manager
that referenced
this issue
Dec 20, 2016
Travis only runs a subset of tests via `npm run test_travis`, but `npm test` runs a full suite. See angular#165 for details on why travis cannot run all tests.
sjelin
added a commit
to sjelin/webdriver-manager
that referenced
this issue
Dec 20, 2016
Travis only runs a subset of tests via `npm run test_travis`, but `npm test` runs a full suite. See angular#165 for details on why travis cannot run all tests.
sjelin
added a commit
that referenced
this issue
Dec 21, 2016
Sadly, x86 emulation is impossible (no hardware extensions on circle) and arm is unworkably slow, so no android tests. See #167 for ideas about work arounds Removed travis tests since circle tests are cooler anyway Made some timeouts longer because I guess circle is slow. Also improved some an error path in downloader because it was a problem while debugging. Sample output: https://circleci.com/gh/sjelin/webdriver-manager/31 Closes #165
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I can't seem to bring up browsers or emulators on travis. I also found this suggestive error message when trying to bring up an android emulator:
https://travis-ci.org/angular/webdriver-manager/jobs/178687294#L1109
To me, this indicates that the issue is that travis lacks a screen. I have had similar problems with
ssh
sometimes. However, I don't think this will be a problem on CircleCI, since our protractor CircleCI tests are clearly able to bring up a browser.The tests may still have to be ARM tests instead of x86 though, since it's not clear if it will be possible to enable hardware acceleration (required for emulating x86),
The text was updated successfully, but these errors were encountered: