351ebd6652
closes: CORE-1874 test plan: Now that the automated selenium & javascript specs pass for this the last thing we need to do is to go manually click around and see if anything breaks. The best thing to do would be to open your browser console and look for errors. Deprecation warnings or propType errors or react warnings are fine but if any actual errors get thrown that is something we want to look into. specific things to look at: * all the gradezilla/gradebook/grading stuff (specifically things that have instUI <NumberInput>s and <Select>s) * look at the submission cell editor * the gb headers (especially make sure keyboard navigation works how it should) * moderated grading * grading perid edit page / enrollment terms * speedgrader * grading standards * gradebook history * theme editor * new discussions/announcements * the new permissions page * the dasboard * student planner * dashcards * global nav trays * help menu * assignment edit page * account user/course search Change-Id: I6a1fe7df9379d9c601eda932bd8cef9c06d10cd2 Reviewed-on: https://gerrit.instructure.com/163913 Reviewed-by: Clay Diffrient <cdiffrient@instructure.com> Tested-by: Jenkins QA-Review: Jeremy Putnam <jeremyp@instructure.com> QA-Review: Tucker McKnight <tmcknight@instructure.com> Product-Review: Clay Diffrient <cdiffrient@instructure.com> Product-Review: Ryan Shaw <ryan@instructure.com> |
||
|---|---|---|
| .. | ||
| package.json | ||