Speaker 2
Um, and in fact, I
Speaker 3
remember, uh, Will from our Slack community, he and I had debated one time
Speaker 2
because, uh, we were talking about that and he, he kind of thought like, Oh yeah, I do like that because the idea was that no matter what the test runner is, right, you can immediately see like, Oh, I can see what's being tested. I can see the scenario that might have
Speaker 3
failed and whatnot and what was expected. Like I don't have to go look at the code, I can see this from like, uh,
Speaker 2
if the test runner was a command line, if the test runner was a team city or a Jenkins or whatever, right? And, and at the time, I remember Will and I got into this debate where it was like, Oh, maybe even the class name should be,
Speaker 2
you know, prepent be propended to it. So it'd be like the class that's under test, underscore method, under test, underscore scenario, underscore, um, result. So, and so all of that is to say like that was heavily influenced by, you
Speaker 3
know, Roy Oshirov, his,
Speaker 2
his naming standard that he had advocated for back when that book came out, which in fairness, I think that book came out like 2009. I don't know if when you go and check that, but I'm pretty sure that's when that book came out. So this book, the unit testing, uh, three P, uh, this book's fairly new. I forget exactly what the date of it is. I'm trying to look for it now while I run my mouth 2009, by the way.
Speaker 3
Oh, so I had the other one right. Okay. So this book came out in 2020,
Speaker 3
uh, oh, his name
Speaker 2
is Vladimir and I
Speaker 3
will definitely mess this
Speaker 2
up. Cora Cove, I'm going to say is how I would try to pronounce that. And I'm so sorry, Vladimir, if I
Speaker 3
said that wrong.
