kibana/test/intern_api.js

define({
  suites: [
    'test/unit/api/ingest/index',
    'test/unit/api/search/index',
    'test/unit/api/scripts/index'
  ],
  excludeInstrumentation: /(fixtures|node_modules)\//,
  loaderOptions: {
    paths: {
      'bluebird': './node_modules/bluebird/js/browser/bluebird.js',
      'moment': './node_modules/moment/moment.js'
    }
  }
});
Give API tests their own intern config Adding a 'suites' property to the existing intern configuration caused an error to be thrown at the beginning of the functional test run. Even if the value of 'suites' was just an empty array. The existence of the property seemed to enabled execution of the config file in the selenium browser because it complained about not having the node require function. To fix this, I created a separate api test config file without the node require and removed the 'suites' property from intern.js. 2015-11-20 18:58:58 +01:00			`define({`
			`suites: [`
Count API - count the number of documents in an index pattern 2016-03-14 22:13:32 +01:00			`'test/unit/api/ingest/index',`
Add a new GET script languages API endpoint To provide additional language options for scripted fields, Kibana needs to know what languages are available for inline scripting in Elasticsearch. This new Kibana API grabs up to date information from Elasticsearch and provides it in an easy to digest format for the UI. The response body from the API is a simple JSON array with a list of languages that are enabled for inline scripting. The API also filters out languages that don't make sense in scripted fields, like 'mustache'. An example request might look like this: `GET /api/kibana/scripts/languages` 200 OK `['expression', 'painless']` 2016-07-09 15:40:15 +02:00			`'test/unit/api/search/index',`
			`'test/unit/api/scripts/index'`
Give API tests their own intern config Adding a 'suites' property to the existing intern configuration caused an error to be thrown at the beginning of the functional test run. Even if the value of 'suites' was just an empty array. The existence of the property seemed to enabled execution of the config file in the selenium browser because it complained about not having the node require function. To fix this, I created a separate api test config file without the node require and removed the 'suites' property from intern.js. 2015-11-20 18:58:58 +01:00			`],`
			`excludeInstrumentation: /(fixtures\|node_modules)\//,`
			`loaderOptions: {`
			`paths: {`
			`'bluebird': './node_modules/bluebird/js/browser/bluebird.js',`
			`'moment': './node_modules/moment/moment.js'`
			`}`
			`}`
			`});`