"You've made no mention of the low results, nor the variability in the results. It's like you've drawn a conclusion and are laser focused only on the data that supports it. I've looked at every post you've posted in this thread. You question the intellectual curiosity of CR's review staff, but you're exhibiting a lack of it yourself. "
Respectfully, you are so wrong. I haven't mentioned the low end numbers because they are within the realm of possibility, especially for a device that has known battery life issues. I can think of all sorts of explanations for a computer having poor battery life; dGPU kicked in too often, firmware not programming ASICs properly, incomplete charge profile, poor or variable CPU/ASIC yields with high sidewall capacitance leakage under certain conditions, partially defective battery, battery charger not producing enough current during the charge cycle, display leakage abnormalities, and on and on.
For the life of me, though, I can't think of any hardware issues that would increase the manufacturer's maximum battery life by 85% while running real-life usage test scenarios. Can you?
"Not once in any post have you even mentioned the possibility that the MBP might have an issue."
Not true. In the past I speculated Apple would resolve the very real issue with a software/firmware update. This would not be the first time that has happened. And thus I'm not surprised.
"If that aspect of the overall test wasn't flawed, why shouldn't we have any confidence in their overall results? "
That's easy. It was likely flawed. Can you come up with an objective and meaningful real-life usage scenario (web browsing, watching videos, etc) that would result in 18 1/2 hours of usage? For any laptop, Apple or otherwise?
"This is full of assumptions citysnaps. Chief among them, is the assumption they didn't check their equipment. "
Sorry, wrong again. Those were not assumptions. I listed them as possibilities that could lead to absurdly high battery life numbers achieved in a real-life use test scenario. You may not be aware that during acceptance testing of products, when abnormal results are obtained without explanation, engineers will think about possible causes. Never assumptions, they are possibilities to investigate.
"With respect, you don't know this to be true. It fits with the conclusion you've already drawn so it seems you've convinced yourself it actually happened. "
Nope. I drew a conclusion based on the numbers reported being absurdly high, and not able to think of a real life usage battery test scenario that would generate such high numbers in one situation and low numbers in another. As I said, I have no problem believing the low numbers - all sorts or possibilities that could cause that.
At what point would you become suspicious, seeing as though 18 1/2 hours in a real-life usage test scenario apparently doesn't raise your eyebrows?
Would 25 hours do it? 35 hours? There must be some number that you would stand back and say, "Wait a minute, that can't possibly be true."
It would be like Consumer Reports testing, say, a Lexus 460 V8 off the lot. And over a closed loop test course, and rigorous test procedures, come up with, over multiple tests, MPGs of 5, 7, 12, 15, 18, 20, 24, and 44 MPG.
I'd expect numbers in the range of 15 to 24 MPG, even 12 in some situations. 5 and 7 MPG could be explained by (a combination of) bad timing, improper fuel/air mixture, a brake caliper piston or two stuck, very under inflated tires, etc.
But I know of no situation that could possibly yield 44 MPG over a closed loop course (i.e. not all down hill). Can you think of one? Would that number surprise you? If not, why not? If that number was reported by CR before investigation, would it cast doubt in your mind about their test procedures in general? It sure would with me.
-----------
EDIT:
I forgot that CR mentioned a 19 1/2 hours battery life number. That's +95% over Apple's stated maximum battery life.