827442b4b0
## Summary
Test cases for signals and aliases, including a failure of where we do not copy alias data at the moment even if the target is an ECS compatible field.
For example with this mapping:
```json
{
"dynamic": "strict",
"properties": {
"@timestamp": {
"type": "date"
},
"host": {
"properties": {
"name": {
"type": "alias",
"path": "host_alias.name"
}
}
},
"host_alias": {
"properties": {
"name": {
"type": "keyword"
}
}
}
}
}
```
If we detect this as a signal hit we should be copying over both:
* `host_alias.name` -> `host.name`
* `host_alias.name` -> `host_alias.name`
to the target signal index, but we only copy:
* `host_alias.name` -> `host_alias.name`
### Checklist
- [x] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios
|
||
|---|---|---|
| .. | ||
| apps | ||
| es_archives | ||
| page_objects | ||
| screenshots/baseline | ||
| services | ||
| config.coverage.js | ||
| config.edge.js | ||
| config.firefox.js | ||
| config.js | ||
| config_security_basic.ts | ||
| ftr_provider_context.ts | ||
| README.md | ||
Kibana Functional Testing
See our Functional Testing Guide