- Have you verified your change doesn't have any negative impact when using different browsers?
- Safari
- Chrome
- Firefox
- Internet Explorer
- Edge
- Have you verified your change doesn't have any negative impact when viewing it on a mobile or tablet device?
- Have you verified your change doesn't have any negative impact when viewing it when resizing the browser?
- If you've created a text box for user input, have you verified your change can accept long strings of text and it's still able to be viewed in a friendly way on different browsers, on mobile/tablet devices, and when resizing the browser?
- If you've created a text box for user input, have you ensured new lines are handled in a way that's consistent with how we handle new lines in other areas of the application?
- Have you verified that there are no console errors when viewing your change?
- What happens to the UI when not all the data is present? Does that negatively impact the user experience and/or styling?
- If you made a change to a component used in multiple places, do your Testing Notes account for ensuring we're seeing the expected behavior in every piece of functionality that uses the component?
Last active
June 17, 2020 15:42
-
-
Save case-eee/484165286c9c3a293fd0c96f0b1d3bcc to your computer and use it in GitHub Desktop.
Frontend Changes Checklist
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment