mirrors/electron
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions 1

Remove more words (#12852)

Browse source 
* remove 'basically' from docs

* remove 'simply' from docs

* remove most uses of 'just' from docs
This commit is contained in:
Charles Kerr 2018-05-08 00:16:09 -05:00 • committed by GitHub
parent 86d023b02f
commit 4d078fdb03
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
32 changed files with 51 additions and 52 deletions
Download patch file Download diff file Expand all files Collapse all files

6
docs/tutorial/testing-on-headless-ci.md
View file

@ -1,7 +1,7 @@
# Testing on Headless CI Systems (Travis CI, Jenkins)
Being based on Chromium, Electron requires a display driver to function.
If Chromium can't find a display driver, Electron will simply fail to launch -
If Chromium can't find a display driver, Electron will fail to launch -
and therefore not executing any of your tests, regardless of how you are running
them. Testing Electron-based apps on Travis, Circle, Jenkins or similar Systems
requires therefore a little bit of configuration. In essence, we need to use
@ -20,11 +20,11 @@ for `$DISPLAY`, so no further configuration of your app is required.
This step can be automated with Paul Betts's
[xvfb-maybe](https://github.com/paulcbetts/xvfb-maybe): Prepend your test
commands with `xvfb-maybe` and the little tool will automatically configure
xvfb, if required by the current system. On Windows or macOS, it will simply
xvfb, if required by the current system. On Windows or macOS, it will
do nothing.
```sh
## On Windows or macOS, this just invokes electron-mocha
## On Windows or macOS, this invokes electron-mocha
## On Linux, if we are in a headless environment, this will be equivalent
## to xvfb-run electron-mocha ./test/*.js
xvfb-maybe electron-mocha ./test/*.js