CloudServices/Testability/Questionnaire: Difference between revisions
< CloudServices | Testability
Jump to navigation
Jump to search
(Initial draft.) |
(Tighten up lines.) |
||
| Line 1: | Line 1: | ||
= Testability questionnaire = | = Testability questionnaire = | ||
* create questionnaire for project status/information collection (how | * create questionnaire for project status/information collection (how is testing done, where are the plans, servers, docs, etc.) | ||
== Basic Questions == | == Basic Questions == | ||
# Fill out all the available information in the [Wiki project template]. | # Fill out all the available information in the [Wiki project template]. Are there missing pieces? | ||
# Are there automated tests? Where do they live? Where do they run? How often? Who is in charge of making sure they run? | |||
# Do developers check the results themselves, or is someone in QA responsible for flagging failures? | |||
# Are there automated tests? Where do they live? Where do they | # Who is responsible for manual testing? Is it the QA contact in the template, or someone else? Who flags manual test failures, and who is responsible for escalating them? | ||
# Do developers check the results themselves, or is someone in QA | |||
# Who is responsible for manual testing? Is it the QA contact in | |||
== Follow-up Questions (Community focused) == | == Follow-up Questions (Community focused) == | ||
# What is the current on-boarding process for dev contributors in | # What is the current on-boarding process for dev contributors in your area? | ||
# Is it any different for QA contributors? | |||
# When was the last time anyone reviewed the existing documentation? | |||
# Is it any different for QA contributors? | # Is there any sort of documentation review process, or will we have to invent it? | ||
# Sustainability – can we convince people to make time to keep the onboarding docs in good shape? | |||
# When was the last time anyone reviewed the existing | |||
# Is there any sort of documentation review process, or will we | |||
# Sustainability – can we convince people to make time to keep | |||
Revision as of 17:31, 30 December 2015
Testability questionnaire
- create questionnaire for project status/information collection (how is testing done, where are the plans, servers, docs, etc.)
Basic Questions
- Fill out all the available information in the [Wiki project template]. Are there missing pieces?
- Are there automated tests? Where do they live? Where do they run? How often? Who is in charge of making sure they run?
- Do developers check the results themselves, or is someone in QA responsible for flagging failures?
- Who is responsible for manual testing? Is it the QA contact in the template, or someone else? Who flags manual test failures, and who is responsible for escalating them?
Follow-up Questions (Community focused)
- What is the current on-boarding process for dev contributors in your area?
- Is it any different for QA contributors?
- When was the last time anyone reviewed the existing documentation?
- Is there any sort of documentation review process, or will we have to invent it?
- Sustainability – can we convince people to make time to keep the onboarding docs in good shape?