I am a front-end Web developer who works for a small company. I also do some freelance work on the side occasionally. I would describe my skill set as more design-heavy than programming-heavy.
I have a pretty good set of tools for testing. My Mac runs OSX apps, IE6-11 with VirtualBox, and iOS Simulator; a Nexus 7 gives me an Android touch environment to round out the majority of browsers I should be testing.
What I'm lacking is any real QA protocol. My workflow usually consists of: Develop in Firefox, jump over to Chromium occasionally to make sure nothing obvious is going wrong, and then later in the process open up the VMs and start clicking around a bit to make sure nothing is really amiss.
This is hardly rigorous, definitely not standardized, and probably not even the best way to go about doing things. However, I can't imagine myself testing 10-15 browsers after every change either.
I'm not looking to do a tester's full-time job with the last ten percent of my time - I understand and respect the position's importance more than that. But in an imperfect world where I have to rely mostly on myself for testing, what are some good strategies for doing QA, striking a balance between thoroughness and efficiency?
If that's too broad of a question, I'd like to focus on front-end design specifically more than things like 'does the data validate'.