[ftr] add first-class support for playwrite journeys#140680
[ftr] add first-class support for playwrite journeys#140680spalger merged 22 commits intoelastic:mainfrom
Conversation
0ba6e73 to
1161887
Compare
|
Sorry about that @dmlemeshko, my migration of the config file to not need the removed |
|
Thank you @spalger, I retested and scalability run works perfectly now |
💚 Build Succeeded
Metrics [docs]Public APIs missing comments
Any counts in public APIs
Public APIs missing exports
Unknown metric groupsAPI count
ESLint disabled in files
ESLint disabled line counts
Total ESLint disabled count
History
To update your PR or re-run it, just comment with: |
Fixes #140676
This PR enables the FTR to load a custom "journey" format config file (example). This config file format is a big iteration on the FTR config file format, but using the
@kbn/journeyspackage can be converted into the components necessary for journeys to behave like standard FTR configs, meaning that journeys can be defined cleanly and in a focused way without making major changes to the FTR or creating a new test runner.For a comprehensive example of how journeys look in this new format, checkout x-pack/performance/journeys/web_logs_dashboard.ts.
In addition to improving the ergonomics of journeys this PR ensures that failed steps trigger failures, something that wasn't happening before. This requires that journeys are very stable, so the stability of existing journeys was improved and debugging was improved in this PR by adding screenshots taken at the end of each step to failure reports and ensuring that these reports are uploaded in hourly SUPT jobs (example)
Verified changes to performance pipeline in https://buildkite.com/elastic/kibana-pull-request/builds/72898