Password Reset Poll

[Mania]

Guess how many times I've had to reset my own password on Warcraft Mounts in the past 24 hours, in order to test password reset on the live site.

Bonus points if you can name the two separate reasons I am testing it live.

[Saturo]

I'm guessing 12, with the reason being evil people, like me.

[Chrizesu]

How come there's no option 42?

[Sarayana]

Because you improved the feature? Because you're checking for repeats? Because you found an error in the coding? Uhmm... Because you were bored and had nothing better to do? @_@

[Mania]

Ah, I didn't mean why I was testing it, but why I was testing it on the live site instead of on my local testing environment like a good developer.

[Sarayana]

... because you're lazy? ;P Haha just kidding, I've no idea.

[Dakonic]

Because you wanted too. =] Haha I don't know.

[Mania]

The correct answer ended up being 13 because I had to do one more test after I posted the poll. *sigh* But I expected it to be 12.

And as for the reasons: I run an Apache webserver on my home computer, of course (who doesn't?), but I don't have a mail server set up locally. So for e-mail sending, the final tests must unfortunately always be made on the live site.

Generally that only means one test when I am done with everything else, though. This time I ran afoul of something I didn't even know about before, although I should have: I'm running different versions of the Zend framework at home and on the live server.

One of the changes in the newer version relates to what gets returned from a database call when there are no matching rows. The code was doing an explicit check (===) against the old return value of null, but the new return value is FALSE, so the explicit check failed. Of course, it's easy enough to change that to a loose check (==) or change what you are checking against, but that's hard to do when you don't know what happened and can't figure out why the code has EVER worked on the live site.

[Sarayana]

Haha. I'm so glad I don't have to do that. Mind you, my work isn't very different... After all, I work with databases too, just the statistical kind. We speak the same language, just different dialects.

[Saturo]

1 PRINT YAY!
2 GOTO 1

[Rhyela]

The correct answer ended up being 13 because I had to do one more test after I posted the poll. *sigh* But I expected it to be 12.

And as for the reasons: I run an Apache webserver on my home computer, of course (who doesn't?), but I don't have a mail server set up locally. So for e-mail sending, the final tests must unfortunately always be made on the live site.

Generally that only means one test when I am done with everything else, though. This time I ran afoul of something I didn't even know about before, although I should have: I'm running different versions of the Zend framework at home and on the live server.

One of the changes in the newer version relates to what gets returned from a database call when there are no matching rows. The code was doing an explicit check (===) against the old return value of null, but the new return value is FALSE, so the explicit check failed. Of course, it's easy enough to change that to a loose check (==) or change what you are checking against, but that's hard to do when you don't know what happened and can't figure out why the code has EVER worked on the live site.

......I know what the word "test" means!!! Beyond that I have no idea what you just said.

[Saturo]

Essentially, she had different versions of the server program, and each version dealt with the input in a different way. One didn't respond at all, and the other one gave an internal error message.