“The concept of asking when drafting the acceptance criteria how a Feature will be automated and following through with a precise plan of developing the automated functional tests from design to implementation in the CI / CD pipeline.”
The Shift Down process should force the team to begin answering the following questions as Shift Down Acceptance Criteria:
What are the guidelines for defining web elements?
Are you creating web elements that are unique and not random?
What are the functional areas of the application impacted?
What triggers will be used to execute the automated tests?
These are just a few questions and thoughts we, as a community of developers and test engineers, need to converge to ensure we put automation on the same par as the user experience. With automation, we can deliver software fast. The user should be concerned about how the feature is automated.