QA Engineering Lead @pantheon
"Where will your chocolate live?"
"Do you have control over the environment?"
"Is it up-to-date?"
"How do you intend to keep your chocolate shop up-to-date?"
"What are your concerns for keeping your chocolate safe?"
"How fast do you want to be able to render chocolate?"
"What's the most important feature of your chocolate shop?"
"How do you plan on deploying more chocolate?"
This means that you need a configurable virtual environment.
"What ingredients do I need?"
"What ingredients must I keep our of my receipe?"
"What order to features need to be reverted?"
"When do I need to clear caches?"
"What variables need to be configured for development?"
"What variables need to be configured for production?"
"How am I going to manage it?"
"Who wants what and why?"
"What are your edge cases?"
"What actions do you anticipate your users are going to do with the chocolate?"
"What is the context that you anticipate your user taking actions?"
"What is achievable to complete in small steps?"
Testing is always exploratory.
Every environment is different, but your process doesn't need to be.
I am saying: