Aug 1, 2026 · 9 min · 5 segments
Have you ever fixed a failing test by adding a variable to phpunit.xml and moved on, not thinking twice about whether that was actually the right call? In the latest episode of the No Compromises…
So the scenario to set up, what I had observed in the PR that I was commenting on, was that you had added a bunch of values to our PHP unit XML file.
And these were keys that are also specified in the .env.example file.
And so it doesn't matter what they're for, but they're for talking to an external service.
Yeah.
Well, and before you go on too far, let's make sure when we say it doesn't matter what they're for.
The EMV locally is filled up with two different things, right? The dot EMV file.
It's filled up of workflow control and credentials.
So workflow control, I mean, things like is this enabled or is it not enabled? Are we in debug mode? What database do we even like? What connection do we pick? Not the credentials, but what connection? So it's all workflow.
And then there's a second reason for it, which is credentials like API keys, passwords, things like that.
So I just want to make sure that we bring those up, because I think that might be the core of some of the things here, too.
Oh, OK.
All right.
I'm
prepared to be wrong about this.
But so these were credentials, right? These were these were things that you would use to talk to another third party or Some other system, external system.
And the ones you had added were actually things I had coded in a previous PR.
But then I believe what happened is you were working on this code.
Your tests were passing.
Then you ran the whole suite like a good developer.
And some tests failed related to these keys that I had done in the previous PR.
And you're like, ah, Joel, blah, blah, blah.
And then your tests passed and you moved on.
Is that? Yep.
So the scenario to set up, what I had observed in the PR that I was commenting on, was that you had added a bunch of values to our PHP unit XML file.
And these were keys that are also specified in the .env.example file.
And so it doesn't matter what they're for, but they're for talking to an external service.
Yeah.
Well, and before you go on too far, let's make sure when we say it doesn't matter what they're for.
The EMV locally is filled up with two different things, right? The dot EMV file.
It's filled up of workflow control and credentials.
So workflow control, I mean, things like is this enabled or is it not enabled? Are we in debug mode? What database do we even like? What connection do we pick? Not the credentials, but what connection? So it's all workflow.
And then there's a second reason for it, which is credentials like API keys, passwords, things like that.
So I just want to make sure that we bring those up, because I think that might be the core of some of the things here, too.
Oh, OK.
All right.
I'm
prepared to be wrong about this.
But so these were credentials, right? These were these were things that you would use to talk to another third party or Some other system, external system.
And the ones you had added were actually things I had coded in a previous PR.
But then I believe what happened is you were working on this code.
Your tests were passing.
Then you ran the whole suite like a good developer.
And some tests failed related to these keys that I had done in the previous PR.
And you're like, ah, Joel, blah, blah, blah.
And then your tests passed and you moved on.
Is that? Yep.
The rest of this transcript — segmented and speaker-labeled, so you land on the exact moment something was said
Search every transcript — by keyword, by phrase, or by meaning, across every show Radar indexes
Trends — what is surging across podcasts, measured against its own baseline
Alerts — when a name you follow appears in a newly indexed episode
No account is needed to search Radar.
