scout-migrate-from-ftr

Migrate Kibana FTR tests to Scout by analyzing each legacy test, deciding on a UI or API conversion strategy, mapping FTR services and page objects to Scout fixtures, and rewriting `loadTestFile` suites into independent specifications. This process ensures parity and improves test performance.

Mapping FTR services and page objects to Scout requires translating legacy dependencies into Scout fixtures. This structural conversion replaces FTR service injection with fixture-based setups, ensuring adhere to Scout best practices for maintainability and parallel execution.

Restructuring `loadTestFile` suites involves breaking down shared test file dependencies and rewriting them as independent Scout specifications. This suite restructuring eliminates tightly coupled FTR execution flows, enabling better maintainability and parallel execution in the Scout framework.

Deciding between a Scout UI or API test conversion depends on the FTR test's original interaction layer. You analyze whether the test validates visual interface behavior or backend data flows, then strategically convert it to the appropriate Scout test type for optimal coverage.

Migrating a large suite of FTR tests for a Kibana feature is supported by a step-by-step process to analyze each test, determine its optimal Scout equivalent, and refactor it correctly. This ensures structural parity while improving overall test performance.

Migrating FTR tests to Scout improves maintainability by replacing tightly coupled `loadTestFile` suites and services with standalone Scout specifications and fixtures. This modernized structure aligns with current best practices and enables efficient parallel execution.