4 ms·
As a Tester myself, I cannot understand why this is not covered by either unit tests or behavioral tests. Clicking dialog buttons in rapid succession is what
by jenoer 9y ago
As a Tester myself, I cannot understand why this is not covered by either unit tests or behavioral tests.
Clicking dialog buttons in rapid succession is what we (should) do once in a while. Especially in core functionalities such as the login screen.
It's one of the first screens you see as a tester. And you have default usernames, be it enabled or not.
For example, I do not own an iPhone, but at work, I made a bet with my colleague (jokingly) that I could break _something_ on his phone in a few minutes.
I did not have his finger print or pin-code, so I was very limited, I even joked "I don't need that, give it here!"
Finding out I only had a hand full of options, I focused on the emergency dialer.
As any good tester would be curious about, I wanted to check the max field length, so I entered digits, copy/paste it a few times, copy/paste that string, ("wait, no limit? Not even at 1000? why?") and so on, until I noticed the interface became laggy, so of course, I kept going.
Boom, suddenly back at the login screen, tried to open the emergency dialer, but got a full blank white screen, in the meantime the phone started heating up substantially.
Since it was a new Phone (iPhone 7 with iOS 10.x I believe) and the dev getting nervous, we decided to reboot it. That fixed the issue.
(Curious if this is still an issue in iOS 11.x)
TL;DR: As a tester this simple curiosity should be in your blood, and especially covered in behavioral tests when your software has been around for 5+ years.
- Cthulhu_ 9y agoThis bug isn't caused by rapid succession or whatever, it's more of a generic end to end test. In this case someone would have had to write an exact scenario that opens a settings page, unlocks it, types in 'root', no password, presses login and it should not work.
- tyingq 9y agoIn this case, any password works. The blank one is just the initial example. The password is set to whatever you typed, even if nothing.
- jenoer 9y agoRapid succession button clicking usually combines many different tests: - Performance - Usability - Brute-force capabilities - Error handling - And in this case, Security, a bug where trying to log in a couple of times on the Login screen with an empty, or set, password. A test scenario closer to this would be: --- When I am on the login screen And I enter 'root' in the 'Username' field And I enter 'thispasswordisfalse' in the 'Password' field And I press the 'Login' button '10' times Then I should see the text 'Your password is invalid' --- Please note that this issue is not just in the Settings page, it takes place on the login screen as well, that's why I'm shocked, it's such a core functionality, touching so many system components.
- MrMid 9y agoI got my friends Apple Watch stuck last week just by looking at it's features. IIRC it got stuck while using the "flashlight". It suddenly froze, and it took me a while to reboot it (it got stuck once more while rebooting). All in all, it took me about a minute to break it, and around 5 minutes to get it working again. I was getting a bit nervous.