Not so much agile as fragile
39 comments- TAGS:password, profile
- IT TOPICS:Networking, Security
IT pilot fish is testing a new Web site built using an agile methodology. And how's this new development style working out?
"I wanted to test a new feature added to the 'user profile' section," he says. "We had cleverly designed the user profile page to be password-protected, using the same password used to get into the site."
Fish's password gets him into the Web site just fine. But it doesn't work when he tries to get to the user profile page. The system kicks back an error message informing him that he can't use a password containing anything but letters and numbers.
And fish's password contains an underscore character mdash, which the system was perfectly happy to accept when he created it.
No problem, fish figures, I'll just change the password to something the user profile page is happier with.
But he can't do that either. The page that will let him change his password won't accept the password that the Web site has already allowed him to create.
"Apparently our teams didn't design any standard requirements for passwords," grumbles fish. "They just built one password test to create your account, and a different password test for the user profile page.
"Oh, and did I mention that we have several other Web sites, each with password entry code already in place that could have been reused?"
Sharky's standard requirement is that you send me your true tale of IT life at sharky@computerworld.com. You'll get a stylish Shark shirt if I use it. Add your comments below, and read some great old tales in the Sharkives.
Now you can post your own stories of IT ridiculousness at Shark Bait. Join today and vent your IT frustrations to people who've been there, done that.
Print
Email this
Digg this
Slashdot this
