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

Threads P0 smoke testing #19690

Closed
5 tasks done
kittykat opened this issue Nov 10, 2021 · 2 comments
Closed
5 tasks done

Threads P0 smoke testing #19690

kittykat opened this issue Nov 10, 2021 · 2 comments
Assignees
Labels
A-Threads T-Other Questions, user support, anything else

Comments

@kittykat
Copy link
Contributor

kittykat commented Nov 10, 2021

Run an initial testing session to check that we're on the right track.

What we need going into the session

  • List of completed and partially completed tasks based on must haves for P0
  • Pick a time when most of the team can attend (Product, Design and lead developer for the platform must attend)

During the session

  • Lay out standard paths to follow to achieve tasks (test cases with steps)
  • Run through some exploratory test cases (tasks to achieve without steps)
  • Collect defects and enhancements which are found, and make sure to collect accurate reproductions steps with screenshots and screen recordings as needed

Outputs from the session

  • Product processes and files found issues
  • Design reviews any designs to update for findings from session
  • Acceptance criteria on issues updated as needed (by design, product or development)
@daniellekirkwood
Copy link
Contributor

@kittykat It looks like, as we've run the session and finished our debrief, we can close this issue?
We don't need for the issues found to be closed, just triaged?

@kittykat
Copy link
Contributor Author

Indeed, we can close this 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-Threads T-Other Questions, user support, anything else
Projects
None yet
Development

No branches or pull requests

2 participants