# Who is this PR for?

# What problem does this PR fix?

# What does this PR do?

# Screenshot (if adding a client-side feature)

# Checklist

+ [ ] Tested latest version in an Internet Explorer virtual machine? *(If the PR adds Javascript.)*

# Who is this PR for?

# What problem does this PR fix?

# What does this PR do?

# Screenshot (if adding a client-side feature)

# Checklist

*If the PR touches Javascript, follow this checklist. If the PR doesn't touch Javascript, you can delete this checklist.*

*Which features or pages does this PR touch? Make a list here so that you can double-check each affected page in a Internet Explorer before merging. Make one list for the author and another for the reviewer. For more info on how to download and use a Virtual Machine to test in IE, see the README.*

*Examples:*

+ [ ] Author checked latest in IE - Student Profile
+ [ ] Author checked latest in IE - Student Report PDF
+ [ ] Author checked latest in IE - School Overview
+ [ ] Reviewer checked latest in IE - Student Profile
+ [ ] Reviewer checked latest in IE - Student Report PDF
+ [ ] Reviewer checked latest in IE - School Overview

Update Pull Request checklist to guard better against bugs
Update Pull Request checklist to guard better against bugs

+ One of my big learnings from #1276 was that my QA on #1261 wasn't thorough enough. I tested a bunch of the site but not the Student Report, which went down because of a JS bug.

+ This PR makes the checklist feature way more specific. First of all, it asks the PR creator to name the parts of the app that are affected by any JS changes. That way we should be reminded on each PR to do targeted, specific QA before we merge.

+ In addition, it makes separate checklists for the author and for the reviewer. That's because the current checklist format is ambiguous about who should do the QA: the author, the reviewer, or both? I think both so that's how I wrote the checklist.
