mirror of
https://github.com/elastic/kibana.git
synced 2025-06-29 03:24:45 -04:00
4bd80160b2
## Summary This PR adds a test config category to the scout reporting. This allows us to distinguish between UI and API FTR tests. A new property `testConfigCategory` has been added to all FTR configs that don't already inherit it from a higher level config.
28 lines
1 KiB
TypeScript
28 lines
1 KiB
TypeScript
/*
|
|
* Copyright Elasticsearch B.V. and/or licensed to Elasticsearch B.V. under one
|
|
* or more contributor license agreements. Licensed under the Elastic License
|
|
* 2.0; you may not use this file except in compliance with the Elastic License
|
|
* 2.0.
|
|
*/
|
|
|
|
import { FtrConfigProviderContext } from '@kbn/test';
|
|
import { ScoutTestRunConfigCategory } from '@kbn/scout-info';
|
|
|
|
export default async function ({ readConfigFile }: FtrConfigProviderContext) {
|
|
const xPackAPITestsConfig = await readConfigFile(require.resolve('../api_integration/config.ts'));
|
|
|
|
return {
|
|
testConfigCategory: ScoutTestRunConfigCategory.API_TEST,
|
|
testFiles: [require.resolve('./apis')],
|
|
servers: xPackAPITestsConfig.get('servers'),
|
|
services: xPackAPITestsConfig.get('services'),
|
|
junit: {
|
|
reportName: 'X-Pack Monitoring API Integration Tests',
|
|
},
|
|
esTestCluster: xPackAPITestsConfig.get('esTestCluster'),
|
|
kbnTestServer: {
|
|
...xPackAPITestsConfig.get('kbnTestServer'),
|
|
serverArgs: [...xPackAPITestsConfig.get('kbnTestServer.serverArgs')],
|
|
},
|
|
};
|
|
}
|