This tends to be along application versus service developer lines but even then it’s unclear whether functional means process or module level testing and integration means IPC testing, or whether integration testing means module level testing and functional means IPC.
I just checked and it looks like by 2018 if not earlier Fowler had given up on the distinction and used alternately integration vs E2E or service vs UI, citing Mike Cohn.
Even without the Tower of Babel thwarting conversations, testing is hard. I often say that to give people permission to fuck up in tests from time to time, and/or to impress upon them that you have to respect the tests the way we respect guns - they hurt you the moment you take them for granted.
And every time a coworker disagrees with the assertion that tests are hard, it’s someone whose tests I have beef with. Everything is easy if you don’t care about outcomes. Of course I have beef with -everyone’s- tests including my own. Which is why I know they’re hard, because even when you know what you’re supposed to do and try to do it, you don’t get it completely right.
So I keep an eye out for articles trying to rewrite how we are doing testing, because there are some pretty big impedance mismatches between the practice of testing and the goals of testing. And I don’t know if that’s because it’s a sort of Halting Problem, “only” NP-hard, or we haven’t found the correct viewpoint where everything makes sense.
For instance, I think by and large architectural and mechanical diagrams have given way to 3D modeling, because while I can read 3D projections in my sleep, a lot of people squeaked by in that class. We lack an equivalent representation in code testing. Code coverage is still another isomorphic projection that you can’t turn around until you see the object. 2D of code and .5D of coverage and branch execution.