Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Flesh Out and Determine Severity of User Scenarios For Test Plan Use #186

Open
mafriend opened this issue Oct 18, 2018 · 0 comments
Open

Comments

@mafriend
Copy link
Contributor

mafriend commented Oct 18, 2018

Goals: Each sprint, identify a small number of test scenarios from Product Feature Testing Outline to flesh out with full steps and release showstopper status

What does "fleshing out" entail?
Fleshing out entails breaking out the gherkin into automatable steps for the UI product and adding in validation around THEN steps. Most scenarios will be relatively short but others might involve additional steps or configurations in order to start automating them or including them in regression test suites.

How do we categorize severity?
Scenarios are currently being worked on from most critical to least critical. The most critical scenarios are scenarios that would prevent us from deploying if they failed. Least critical scenarios are those that would possibly prevent us from holding up a deploy, but for the most part would just be fixed as part of a hotfix later. Least critical scenarios are ones around edge cases or usecases that only a very few number of our customers encounter and therefore have a smaller impact.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant