The template is updated to add an input that has a default value
We run an upgrade
The user should be prompted for a value for the new input; the default value should not silently be used.
I thought I saw this last week in my manual testing, but the test passes without changing the logic, so I may have been mistaken.
This change involves some refactoring and test util updates because this is the first time that we've tested prompting logic at the library layer (common/*), rather than the Command layer (commands/*) which wraps the library.
This tests an edge case where:
I thought I saw this last week in my manual testing, but the test passes without changing the logic, so I may have been mistaken.
This change involves some refactoring and test util updates because this is the first time that we've tested prompting logic at the library layer (
common/*
), rather than the Command layer (commands/*
) which wraps the library.