You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As a maintainer of this repo, I want to ensure that changes to this repo don't break automated tests when a full installation, including a plugin and theme, are performed by a user.
Ensure these checks run on PRs against this repo and on a schedule.
Use the automatic installation script established in Add Installer Script #7 to ensure that the project is properly configured before testing, emulating user behavior.
Test against a VIP-type repo and a Pantheon-type repo to ensure both targets are supported.
The text was updated successfully, but these errors were encountered:
The AC as listed would be challenging to accomplish with all the mandatory user input prompts. If they were reduced to 'test the defaults' we should be able to get 90% of the way there... if there were --hosting=vip or --hosting=pantheon options, that would make it possible (assuming the rest of the defaults were possible).
@kevinfodness I'm uncertain whether this is actionable yet with the current state of the configure.php script (@srtfisher may be able to validate my brief examination).
In particular, when specifying the three command-line options, the user is still prompted (though the defaults are updated). So running, for instance:
If we remove the fourth AC (test both Pantheon and VIP), we can make some progress here. By leveraging yes or another tool or utility, we could test the 'all the defaults' option, which would be better than nothing. For instance:
(just accept all defaults). Notably, this seems like it would use the Pantheon hosting option as the default:
... alternatively a fragile implementation (would break or act unexpectedly when new options or questions are added or removed) we could supply the responses ahead of time (answer yes, yes, no , no, etc)
User Story
Acceptance Criteria
The text was updated successfully, but these errors were encountered: