I'm 60 years old.
As an embedded developer (hardware and software) with several decades of experience, and several industrial embedded products under my belt, and several dozen (at least!) product spec-testing sessions I have conducted and/or participated in, I know bad test methodology when I see it, and I definitely saw it when CR got insanely disparate results in the testing, and then even suspected that Safari was involved; but STILL just "ran with it", rather than asking Apple if that seemed odd to them.
As for your "Prove it!" challenge, I offer this anecdote: The only person I know who actually owns a 2016 MBP, has a tb 15" model. He hadn't been following any battery complaints, and I hadn't discussed same with him. He is a degreed Electrical Engineer, BTW. So, when I casually inquired as to the battery-life he was getting, here is the snippet of the email exchange (the rest of the conversation was about GarageBand and Logic Pro X) :
ME: BTW, on an unrelated subject, how has your MBP's battery life been?
FRIEND: I can sit and read/write/surf for a couple of hours and it drops to around 85%. Of course, that's not heavy use, but it does keep the display lit full time - which is probably a bigger drain on the battery than some things. It charges very slowly if you use an adapter not rated for the MBP - no surprise there
Then, in my Reply to that email, I explained a bit why I was asking, and asked a couple of other things, and he subsequently responded:
ME: But you're not seeing sh** like run times of just a couple of hours TOTAL, right?
FRIEND: No, I've never pushed it past a couple of hours, but it has never acted up at all. In fact, I'll usually make it sleep instead of powering down, and 8-10 hours later I'll wake it to show about the same power level as when I put it down and I'll get even more time out of it before I set it aside and plug it in to recharge. I know you're supposed to run it low about once a month, but I haven't gotten around to trying that yet. When I do, I'll probably see just how long a charge lasts.
ME: 2 hours for 15% battery usage is right on-track for Apple's 10 hours for that sort of activity.
ME: What Browser?
FRIEND: Firefox - which, incidentally HATES being put to sleep and crashes. No data loss, but ouch.
And that was the end of that. I agree it is anecdotal "evidence"; but that's all we're getting from these other "I only get [x] hours" posts, anyway, right?
And at least I have tried to actually "Prove it". Not scientific; but at least I have tried...
[doublepost=1484289750][/doublepost]
Crappy test that is still not "real-world" enough for a highly power-optimized CPU like Skylake, coupled with a highly power-optimized OS like macOS Sierra. I suspect that, even with Caching turned off on Safari, the repetitive and predictive nature of CR's testing was being predicted by macOS, and it was actually able to take measures to "sleep" some parts of the CPU, etc. that Apple's test did not allow (or allow as much).