Skip to content

Adding more explanatory note on reordering integration tests to avoid cold-start failures #1301

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.

Sign up for GitHub

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

Merged
ivanovac merged 2 commits into from
Jul 7, 2026
Merged

Adding more explanatory note on reordering integration tests to avoid cold-start failures #1301

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
957c783
Fix: Reorder integration tests to avoid cold-start failures
ivanovac Jul 3, 2026
9bc2ec9
Merge branch 'master' into fix-composer-security-advisory-failures
ivanovac Jul 7, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 3 additions & 1 deletion src/php/integration/init_test.go
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -70,7 +70,9 @@ func TestIntegration(t *testing.T) {
// Expect(err).NotTo(HaveOccurred())

suite := spec.New("integration", spec.Report(report.Terminal{}), spec.Parallel())
// Reordered: Moved "Default" to second position to test if failure is position-dependent
// Note: Test order matters due to CF environment cold-start issues.
// The first test to execute sometimes hits HTTP 500 errors during app push.
// Running "Modules" first (instead of "Default") avoids this issue.
suite("Modules", testModules(platform, fixtures))
suite("Default", testDefault(platform, fixtures))
suite("Composer", testComposer(platform, fixtures))
Expand Down
Loading