kibana/x-pack/test/scalability
Tiago Costa 3a040a170a
chore(NA): rename journeys folder into journeys_e2e inside x-pack/performance to correctly classify journey e2e files (#178340)
The source code classifier we currently have was incorrectly classifying
e2e journey files as `non-package` instead of `tests or mocks` as it was
not using the name standards we used for FTR files.

We could have created a `functional-tests` package for the performance
folder (which is what we want to do in the future) but because we don't
have the feature to create ownerless packages it would not be easy to
find a given owner for that folder.

As such I'm just opting for a second solution which is applying the same
name standards to this journeys folder as we have for FTR and changing a
little the classifier to recognise it.

This should fix the problem found at
https://github.com/elastic/kibana/pull/178017.

Co-authored-by: Alex Szabo <alex.szabo@elastic.co>
2024-03-14 21:15:57 +00:00
..
apis [data views] cache field caps requests (#168910) 2024-01-16 06:54:38 -06:00
fixtures/kbn_archiver [Telemetry] Add scalability tests for known bottlenecks (#151110) 2023-03-10 10:45:36 +01:00
config.ts chore(NA): rename journeys folder into journeys_e2e inside x-pack/performance to correctly classify journey e2e files (#178340) 2024-03-14 21:15:57 +00:00
disabled_scalability_tests.json [scalability testing] add json to track skipped journeys (#151629) 2023-02-21 17:58:50 +01:00
events_shipper.ts Benchmark single apis (#146297) 2023-01-09 16:38:30 +01:00
ftr_provider_context.ts
report_parser.ts Benchmark single apis (#146297) 2023-01-09 16:38:30 +01:00
runner.ts [scalability testing] get the correct Gatling report (#153089) 2023-03-10 13:55:34 +01:00
types.ts [performance] use journey own ftr config to run scalability test (#152596) 2023-03-07 13:20:21 +01:00