From 8661291bf2644f9ee7ee1a82be36cf736d11167f Mon Sep 17 00:00:00 2001 From: Riddhesh Sanghvi Date: Fri, 20 Nov 2026 06:41:20 +0530 Subject: [PATCH] test(behat): seed the latest PHP row instead of creating it site-type-wp and site-type-php now store `--php=latest` as the concrete default version, so a site created with `--php=latest` no longer has a `latest` row. The fixture is created on the default version and its row set to `latest` with the existing database step (undone after the scenario), so the runtime-resolve branch stays covered with or without that change. --- features/dash-sites.feature | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/features/dash-sites.feature b/features/dash-sites.feature index bb42a3f..0e445ab 100644 --- a/features/dash-sites.feature +++ b/features/dash-sites.feature @@ -92,8 +92,10 @@ Feature: ee dash init site sync {"site_type": "wp", "multisite": "subdir", "table_prefix": "wp_"} """ + # New sites store `--php=latest` as the concrete default version, so the `latest` row older releases stored is set directly. Scenario: A site on PHP "latest" is posted with the version it really runs - Given the test site 'bh-dash-command-4.test' exists, created with '--type=php --php=latest' + Given the test site 'bh-dash-command-4.test' exists, created with '--type=php' + And I set the column 'php_version' to 'latest' for the site 'bh-dash-command-4.test' in the EasyEngine database When I run "bin/ee dash init --api=bh-dash-{RUN_ID} --org=bh-dash-org --ip=203.0.113.10 --hostname=bh-dash.example.test" in the EasyDash sandbox Then the return code should be 0 And the site 'bh-dash-command-4.test' should have 'php_version' set to 'latest' in the EasyEngine database