[tests] Rename apps option to appSuites so we don't override the inte…

…rn.apps object

CONTRIBUTING.md

@@ -149,7 +149,7 @@ Run the tests for just your particular plugin. Assuming you plugin lives outside
 The following will start Kibana, Elasticsearch and the chromedriver for you. To run the functional UI tests use the following commands
 
 `npm run test:ui`
-Run the functional UI tests one time and exit. This is used by the CI systems and is great for quickly checking that things pass. It is essentially a combination of the next two tasks.  This supports options `--grep=foo` for only running tests that match a regular expression, and `--apps=management` for running tests for a specific application.
+Run the functional UI tests one time and exit. This is used by the CI systems and is great for quickly checking that things pass. It is essentially a combination of the next two tasks.  This supports options `--grep=foo` for only running tests that match a regular expression, and `--appSuites=management` for running tests for a specific application.
 
 `npm run test:ui:server`
 Start the server required for the `test:ui:runner` tasks. Once the server is started `test:ui:runner` can be run multiple times without waiting for the server to start.

tasks/config/intern.js

@@ -10,7 +10,7 @@ module.exports = function (grunt) {
       reporters: ['Console'],
       grep: grunt.option('grep'),
       functionalSuites: grunt.option('functionalSuites'),
-      apps: grunt.option('apps')
+      appSuites: grunt.option('appSuites')
     },
     dev: {},
     api: {

test/functional/index.js

@@ -25,7 +25,7 @@ define(function (require) {
       const option = arg.split('=');
       const key = option[0];
       const value = option[1];
-      if (key === 'apps' && value) return value.split(',');
+      if (key === 'appSuites' && value) return value.split(',');
     });
 
     const apps = [