Comment Re:Does anyone know what "preview" means? (Score 1) 56
It's actually pretty understandable.
Despite the meme power of a broken login, the bug affects a fallback feature you might well go years without using.
It requires you have PIN/Touch sign in enabled; which if you've enabled that, that means that is how you normally login.
And that works just fine. Nothing is broken there.
What is missing is a "password" icon in the 'fallback' options to "sign in a different way" (using a password, e.g., instead of a PIN or fingerprint.)
So despite being on the login screen, its not actually something you are going to regularly interact with normally, unless you forgot your pin or something. And its hardly something human beta testers are going to think to explicitly test for, every single build. And since the bug is a missing element as opposed to a visibly broken element, well, its easy to fail to notice something you almost never use isn't there.
Meanwhile, clicking where its supposed to be still actually works, so its entirely plausible that you could have automated test scripts that continue to pass if they've been scripted to click at coordinate (X,Y), or to select the password button programmatically by an identifier or something, and then 'expect' something to happen in response, because the button is there and it works just fine, its just missing its texture or something. This would slip past a lot of test frameworks, the button is "in the model", "its active/enabled", "its selectable", "its clickable", and "it fires a click event if you click", "and whatever it is supposed to do happens", and its probably even "visible" (though you can't see it); most likely the icon or texture is missing or unassigned or referencing a transparency by mistake, and its just a "transparent button". So unless you specifically add checks to screen capture and compare a pixel block range to a reference image bitmap or something, you aren't even going to catch it with an automated test.
Tests like THAT do exist and can be written, but its not usually very useful, and the cost to write and maintain such tests with reference images is huge. change an icon or font or background color and a zillion tests need to be updated. Its a difficult balancing act to decide what to test, even for a highly competent QA team.
It's possible it just outright incompetence too... but in this case, for this bug... its pretty understandable.