-
Notifications
You must be signed in to change notification settings - Fork 8.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Automation Plan: Kibana Visual Testing #33817
Comments
This should be a separate test suite, need to figure out organization. |
Development of features for visual testing has been available/open to add tests across each Kibana functional area for a few months now, at that time we had PR checking limited to only visual testing PRs, however now we have decided to enable visual testing against every PR as part of #42989 I have been running stability tests for Percy with our existing tests and so far Canvas and Maps seem pretty stable. There are still issues I am investigating with the other areas, more updates to follow. |
This describes the initial test plan and infrastructure work for Kibana visual testing. Evaluating using a commercial tool for visual testing. Also researching cypress.io for visual testing to see if it helps with test flakiness.
We currently have close to 800 functional tests in Kibana repo for selenium and x-pack.
I went through build statistics to see how many runs per month over the last year.
I went through existing test count on latest kibana repo master, excluding tests for: intake, plugin, interpreter, graph, home, getting started, context, dev tools, management, logstash pipeline, rollup, watcher, security, API, upgrade, spaces.
Existing test count should be filtered down further for what will be part of a visual test suite and we need to add any missing coverage. We can group different types of visualizations into a dashboard or different canvas elements into one workpad for consolidated checks to reduce number of tests.
(More than one engineer can be assigned to work on a functional area and can be directly or indirectly involved in the test dev)
(*feature means it is owned by Kibana team )
Estimating snapshot checks: (No of tests) x (3 browsers available) x (No of runs) x (growth factor)
Only Chrome and Firefox currently available in commercial tools, IE to be added later, not sure about Safari.
Test Plan
TBD
The text was updated successfully, but these errors were encountered: