{"action":"opened","issue":{"url":"https://api.github.com/repos/elastic/kibana/issues/20948","repository_url":"https://api.github.com/repos/elastic/kibana","labels_url":"https://api.github.com/repos/elastic/kibana/issues/20948/labels{/name}","comments_url":"https://api.github.com/repos/elastic/kibana/issues/20948/comments","events_url":"https://api.github.com/repos/elastic/kibana/issues/20948/events","html_url":"https://github.com/elastic/kibana/issues/20948","id":342462071,"node_id":"MDU6SXNzdWUzNDI0NjIwNzE=","number":20948,"title":"Create Elasticsearch Reporters for indexing test results","user":{"login":"LeeDr","id":13542669,"node_id":"MDQ6VXNlcjEzNTQyNjY5","avatar_url":"https://avatars1.githubusercontent.com/u/13542669?v=4","gravatar_id":"","url":"https://api.github.com/users/LeeDr","html_url":"https://github.com/LeeDr","followers_url":"https://api.github.com/users/LeeDr/followers","following_url":"https://api.github.com/users/LeeDr/following{/other_user}","gists_url":"https://api.github.com/users/LeeDr/gists{/gist_id}","starred_url":"https://api.github.com/users/LeeDr/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/LeeDr/subscriptions","organizations_url":"https://api.github.com/users/LeeDr/orgs","repos_url":"https://api.github.com/users/LeeDr/repos","events_url":"https://api.github.com/users/LeeDr/events{/privacy}","received_events_url":"https://api.github.com/users/LeeDr/received_events","type":"User","site_admin":false},"labels":[{"id":140008186,"node_id":"MDU6TGFiZWwxNDAwMDgxODY=","url":"https://api.github.com/repos/elastic/kibana/labels/test","name":"test","color":"5319e7","default":false}],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2018-07-18T19:32:47Z","updated_at":"2018-07-18T19:32:47Z","closed_at":null,"author_association":"CONTRIBUTOR","body":"**Describe the feature:**\r\nWe have an ongoing issue with Flaky tests.  While these are mostly UI tests I think it would benefit us to have the capability to load all automated test results into an Elasticsearch instance so we can drink our own champagne and use Kibana to quickly see the biggest issues\r\n\r\n**Describe a specific use case for the feature:**\r\nGenerally speaking, there are configurable reporters for more test frameworks that can log to the console and/or create junit test output and/or html reports, etc. and have a mechanism for plugging in another reporter.\r\n\r\nWe can use this issue to define requirements and then individual PRs to implement the reporters.\r\n\r\nFrameworks:\r\n - [ ] Functional Test Runner\r\n - [ ] Elastic Stack Test Framework (ESTF)\r\n - [ ] integration-test framework\r\n - [ ] new Webdriver.IO framework\r\n\r\nIt would be great if we could collect a consistent set of fields in the reporter for each framework, but they may not have all the same data available.  Maybe we just come up with the super-set of what we'd like and each framework can try to capture as much of that as possible.\r\n\r\nMapping:\r\n- timestamp (of the execution of the test)\r\n- version (ex: 6.4.0 or 6.4.0-SNAPSHOT or 6.3.2-0b85b411)\r\n- branch (ex: 6.x)\r\n- testname (made up of each level of describe plus test name like `kibana - settings app - creating and deleting default index - index pattern creation - should have index pattern in page header`?\r\n- suitename (each level of describe but not the test name?)\r\n- result (Pass/Fail)\r\n- error (blank if Pass, stack trace if Fail)\r\n- hostname (could be Jenkins worker)\r\n- runId (we need some kind of job number to group a test run like Jenkins job #,)\r\n- os (currently Jenkins runs CentOS and Ubuntu but eventually will add Windows)\r\n- browser (Chrome, Firefox, IE)\r\n\r\n"}}
{"actor":{"display_login":"LeeDr"}}