“ethics aside” truly a starter for a qa
Ask Robert’); DROP TABLE Students; 's mum how it went.
“We call her Carrie, because of the carriage return.”
You can also try to give the child NULL as middle name for additional fun.
someone tried that with their license plate, it turned out well: https://www.wired.com/story/null-license-plate-landed-one-hacker-ticket-hell/
edit: archive link
I just realized that the shitty software on the other side of the divide is casting null to ”null", which absolutely explains that issue. What a cluster
Oh no, it gets worse:
Prank or not, Tartaro was playing with fire by going with NULL in the first place. “He had it coming,” says Christopher Null, a journalist who has written previously for WIRED about the challenges his last name presents. “All you ever get is errors and crashes and headaches.”
Archive link: https://archive.ph/o/Foe1r/https://www.wired.com/2015/11/null/
He is being too nice. He needs to get a lawyer and sue that shitty company for harassment and whatever else.
ETA: The US isn’t overly litigious. We are under litigious if anything.
Once I was tasked with doing QA testing for an app which was planned to initially go live in the states of Georgia and Tenessee. One of the required fields was the user’s legal name. I therefore looked up the laws on baby names in those two states.
Georgia has simple rules where a child’s forename must be a sequence of the 26 regular Latin letters.
Tenessee seemed to only require that a child’s name was writable under some writing system, which would imply any unicode code point is permissible.
At the time, I logged a bug that a hypothetical user born in Tenessee with a name consisting of a single emoji couldn’t enter their legal name. I reckon it would also be legal to call a Tenessee baby 'John '.
Sounds like you did a thorough job as a QA tester. As a software engineer, I love to see it.
By the time the app was due to go live, we’d only reported bugs with the signup and login flows. This was misinterpreted as there only being issues with the signup and login flows, and the app launched on time. In reality, it was impossible to get past the login screen.
And then let me guess… Of course the QA testers get the blame, when in reality it’s either management or marketing that wanted to pushe the app out.
