Confirmed users
9,511
edits
Webtools/Checklist: Difference between revisions
Jump to navigation
Jump to search
→I think the design work is ready to be tested; what's next?
| Line 24: | Line 24: | ||
## In the bug, note any contingencies/dependencies | ## In the bug, note any contingencies/dependencies | ||
## Be clear as to what work is already completed, what will eventually need to be pushed where and when (the actual call to push is a separate bug), and what still needs to be implemented | ## Be clear as to what work is already completed, what will eventually need to be pushed where and when (the actual call to push is a separate bug), and what still needs to be implemented | ||
# QA and WebDev will investigate whether the project is testable, and if so, QA will write a test plan incorporating a testing approach, support for various browsers, and staging URLS. | # QA and WebDev will investigate whether the project is yet testable, and if so, QA will write a test plan incorporating a testing approach, support for various browsers, and staging URLS. | ||
# QA will then note the testing results--depending on the amount and types-- either directly in the bug or in the test plan (usually both) | # QA will then note the testing results--depending on the amount and types-- either directly in the bug or in the test plan (usually both) | ||
# An empowered member of Marketing (usually they who are leading the project) will--after consulting with QA/WebDev/IT--make the call as to whether to ship | # An empowered member of Marketing (usually they who are leading the project) will--after consulting with QA/WebDev/IT--make the call as to whether to ship | ||