Skip to content
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

[performance testing] Setup isolated user journey tests #98337

Closed
spalger opened this issue Apr 26, 2021 · 1 comment
Closed

[performance testing] Setup isolated user journey tests #98337

spalger opened this issue Apr 26, 2021 · 1 comment
Assignees
Labels
performance Team:Operations Team label for Operations Team

Comments

@spalger
Copy link
Contributor

spalger commented Apr 26, 2021

We need to create a small number of tests that run through specific user journeys in Kibana. These tests might be written using @elastic/synthetics, though some testing should be done to make sure that's a good idea. Synthetics run using Playwright, which is a lower level browser automation and testing tool than we use in our current FTR tests. Unlike other new testing tools, Playwright maintains an API similar to what we get with selenium-webdriver so we should be able to adapt our existing services to work with it. Playwright is also much faster than selenium-webdriver, implying to me that we should be able to get more reliable data from it WRT performance.

When running these tests Kibana should be shipping APM data to ES at a 100% sample rate with spans and transactions labeled so that we can investigate the transactions and spans created in a specific PR or Kibana CI build.

@spalger spalger added the Team:Operations Team label for Operations Team label Apr 26, 2021
@spalger spalger self-assigned this Apr 26, 2021
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-operations (Team:Operations)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
performance Team:Operations Team label for Operations Team
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants