Manual test procedure

[nedtwigg]

We can split bugs in our textarea detection logic into two categories

• false negative - a textarea which we should have enhanced, but did not
  • we can mostly catch these with unit tests
• false positive - a textarea which we should not have enhanced, but did anyway
  • harder problem, there are an infinity of unit tests we could create for this

For both cases, an important limitation we have right now is that we can't do unit tests on dynamic elements that weren't present on the initial page load. So! A checklist! The official checklist will always be in this comment, discussion in this issue will periodically deleted once it has been incorporated.

• go to Change colors to match GitHub's theming #11
  • click edit on the comment
  • edit box ⇒ enhanced
• go to Add HAR files for gh_new_issue and gh_new_pr. #17
  • click edit on the comment
  • edit box ⇒ enhanced
• go to an unmerged PR
  • click merge
  • commit message ⇒ plain

[nedtwigg]

Thanks to our HTML snapshots, we can do these tests automatically now! Huzzah for automatic testing.