Hey #WebMakers: in one tweet describe the QA steps you take, in order, when testing browser compat. #webdev #interoperability #browser #apps

Aug 4, 2015 · 12:39 PM UTC

6
1
1
@kjtten That sounds thorough, especially because you're doing a QA prior to handoff, which is something I think we all should be doing!
@asbig The answer to that is "NO" so what do you do? And which frameworks are you testing? This inquiring mind wants to know! :D
@asbig That all sounds perfectly un-scary!
@andrew_k HA! That's pretty funny - and I bet true for most folks one way or another (but they don't say so ;-) )
@andrew_k I think that's true for most of us. We're not patching for CSS issues left and right, freeing up for cleaner JS all around.
Replying to @mholzschlag
@mollydotcom Markup and css validation and jslint on commit. Selenium tests with screenshots reported run overnight. Manual reviews.
1
1
@ealsmyr Nice and clean process! Impressive. Also, leaving work early on Fridays or be that kid p0wning his moves before a bonk on the head!
Replying to @mholzschlag
@mollydotcom Work through my standard list, which includes browsers, OSs, and devices, and: "sometimes use the web app like a user".
1
1
@TobiReif How many "browsers, OSs, and devices" do you test on, and which ones top your list?
1
Replying to @mholzschlag
@mollydotcom 1) build 2) ship 3) wait for complaints. j/k
1