This doesn't mean that real user data was taken from production planted into intergration tests. Quite plausibly, test code is mixed in with production code, and got somehow accidentally executed in production. Maybe someone opened a live REPL into some running service and stepped on some test function, and that function used its real production context to send an e-mail to a real user. Kind of thing.
Oops HBO, using real user data in your software integration tests?
21–30 of 85 posts
Re: Oops HBO, using real user data in your software integration tests?
#22Yep, got it on 2 different emails — WTH?! What is going on?
Re: Oops HBO, using real user data in your software integration tests?
#23Yes. What the hell? I'd really like to know why.
Re: Oops HBO, using real user data in your software integration tests?
#24wow, this will go down as an all-time tech fail.
Re: Oops HBO, using real user data in your software integration tests?
#25got 3 of them
Re: Oops HBO, using real user data in your software integration tests?
#26YES, LMAO. Someone will not have a great Friday morning team meeting at HBO.
I wonder if we'll find out how many of their subscribers got em.
I got two. Was wondering first if it was suspicious or an oops.
Re: Oops HBO, using real user data in your software integration tests?
#27Yes... I don't have hbo so why do they have my email?
Re: Oops HBO, using real user data in your software integration tests?
#28Yup just got one and went straight to Google to find out wtf was going on. What does it mean?
it means a test that was supposed to check if hbo max's software can send emails correctly was run with their real email authentication somehow. I'm so curious how they managed to send it to so many people!
Re: Oops HBO, using real user data in your software integration tests?
#29This kinda thing gets under my skin.
Re: Oops HBO, using real user data in your software integration tests?
#30Yes