Rename browser testing to remote testing

grengojbo · Jan 26, 2016 · 0d7351f · 0d7351f
1 parent 4f83d4f
commit 0d7351f
Show file tree

Hide file tree

Showing 3 changed files with 10 additions and 4 deletions.
diff --git a/docs/general/commands.md b/docs/general/commands.md
@@ -28,6 +28,8 @@ Gets your application ready for deployment. Optimizes and minifies all files, an
 
 ## Testing
 
+See the [testing documentation](../testing/README.md) for detailed information as to how testing works! If you just want the commands and know how to write tests already, look below!
+
 ## Unit testing
 
 ```Shell
@@ -76,7 +78,7 @@ $ npm run pagespeed
 
 With the development server running (i.e. while `$ npm start` is running in another tab), enter this command to run Google PageSpeed Insights and get a performance check right in your terminal!
 
-### Test around the world
+### Remote testing
 
 ```Shell
 $ npm run serve

diff --git a/docs/testing/browser-testing.md b/docs/testing/browser-testing.md
diff --git a/docs/testing/remote-testing.md b/docs/testing/remote-testing.md
@@ -0,0 +1,7 @@
+# Testing from different locations
+
+```Shell
+$ npm run serve
+```
+
+This command will start a server and tunnel it through with `ngrok`. This'll give you a URL that looks a bit like this: `xxxxx.ngrok.com` This URL will show the version of your application that's in the `build` folder, and is accessible from the entire world! This is great for testing on different devices from different locations!