Nobody's code is perfect, and all browsers don't run that code the exact same way. A developer can be staring at the weirdest issue ever with no clue where to begin troubleshooting. Sometimes, searching Stack Overflow for related issues can feel like an exercise in futility. A developer's mettle can be tested when this happens, so having the right tools and the proper mindset can mean the difference between a five minute fix, and an all-nighter. This repo will serve as a great place for storing tips for troubleshooting, list some great tools, as well as be reference point for new devs who are trying to level up their trouble shooting skill. Please feel free to submit a PR for any extra tools or tips you think should be added to the list.
- Have a (good) browser you know inside and out - Chrome Browser
- Developer Tools
- Network Resources
- Download as HAR File - upload to http://www.softwareishard.com/har/viewer/
- Demo
- Network Resources
- Extensions
- Developer Tools
- Have an isolated browser just for testing: Chrome Canary
open -a Google\ Chrome\ Canary --args --disable-web-security -–allow-file-access-from-files- Helpful with CORS issues for local development
- Know your HTTP response status codes
- Proxy all the things!
- Fiddler
- Charles Proxy
- Looking at your browser traffic is easily handled through Chrome Developer Tools, but Charles can show requests from other applications like the iOS Simulator.
- Most sites are using SSL, so you need to configure Charles for SSL proxying!
- Demo
- Let's change the content of github.com!
- Know your IDE/Editor
- Who cares what the editor is...find the one that YOU are most comfortable with!
- Know your version control tools inside and out
- Learn to love the command line
- Use Postman for API Testing
- Postman
- Demo if time
- Postman
- Emulation