Details
-
Task
-
Resolution: Done
-
Neutral
-
None
-
None
-
None
Description
We have found that some test fail because when attaching the hello-saas git repo only the branch newly created for the test suite is synced into the subscription.
In this scenario the Magnolia admin central environment swicther only shows the branch, and since some test expect there to be the 'main' branch, it causes test failure.
In this cases, we've found that pushing the "sync now" button on the Magnolia Git config form, it forces all the other branches to sync (and hence be shown in the environment swithcer).
We need to discover how the syncing works and either force to always sync the main branch (aside from the current subscription test branch), or provide in the saas-test-framework some method to allow syncing per branch.
If possible we should not enforce to sync all the repo, since controlling what individual branches do sync is even convenient for some test scenarios.