Skip to content
This repository was archived by the owner on Jan 19, 2025. It is now read-only.

Commit 4a3b7b1

Browse files
committed
Fix typo 🚀
1 parent 9ea88ee commit 4a3b7b1

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

_posts/2019-02-08-mobile-ui-test-crossplatform-appium.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -32,7 +32,7 @@ To put in place the e2e infrastructure we chose:
3232
- [Appium desktop App](https://github.com/appium/appium-desktop)
3333

3434
#### **Development**
35-
The first thing we did was installing all the above software on our CI machine. As a consequence of the fact that we want to run tests for both iOS and Android a macOS based CI machine is needed (because you need to install Xcode). Fortunately, our CI machine was already an Apple Computer so we didn't need to change anything.
35+
The first thing we did was installing all the siftware stack previously described on our CI machine. As a consequence of the fact that we want to run tests for both iOS and Android a macOS based CI machine is needed (because you need to install Xcode). Fortunately, our CI machine was already an Apple Computer so we didn't need to change anything.
3636
After that we created a new javascript project, that follows the structure of the [WebdriverIO sample code contained in the Appium github repository](https://github.com/appium/appium/tree/master/sample-code/javascript-webdriverio "appium webdriverio sample"). This sample project is written using ES5 syntax, so we decided to upgrade it to use ES6 syntax and compile it using Babel. This is possible by launching mocha and specifing babel as the compiler. This is the final command to launch our tests:
3737

3838
```shell

0 commit comments

Comments
 (0)