Code Testing Framework - DoSomethingArchive/legacy-website GitHub Wiki

A few helpful questions to ask yourself when testing new (or updated!) code:

Function

  • Is the behavior correct if the action is taken once?
  • Is the behavior correct if the action is taken twice?
  • Can the action be undone? If so, is the behavior correct?
  • Does the action get stored correctly from a data perspective?
  • Does this action correctly trigger (or not trigger) email or SMS transactional messages?

Perspective

  • Is the behavior correct if you are coming from outside the US? Check using TorGuard, our VPN service.
  • Is the behavior correct for members and admins?
  • Is the behavior correct for different levels of admins?
  • Is the behavior correct for members who are logged in and logged out?
  • Is the behavior correct for existing users?
  • Is the behavior correct for new users?
  • Is the behavior correct on the pitch page?
  • Is the behavior correct on the action page?
  • Is the behavior correct if the campaign is open?
  • Is the behavior correct if the campaign is closed?

Dependencies

  • Is the behavior correct everywhere the code is referenced? (e.g. Kudos appear on the action page, in onboarding, on the permalink, on the user profile)
  • Is the behavior correct everywhere the content is referenced? (e.g. email digests pull DO IT tips from Phoenix, the mobile app pulls in the campaign header photo)

Aesthetic

  • Does this adapt to be responsive on mobile (Android and iOS) vs. desktop?
  • Does this look correct across browsers? You can test on browserstack.com.