think about what the developers are "into" and consider a theme. Are they Trekkies? Into drag racing? Fishing? Techno-junque? Is there a favorite classic ( Star Wars, The Hobbit, Xanth ) that has its own language? The team of testers and developers can define words and phrases from that "world," define their specific meaning to the task of creating quality software together...and then communicate in a way that is neutral and fun, in a language that belongs to both sides.
Here's an example. In a shop where drag racing aficionados are at work, a unit test becomes a demo run. A system test becomes initial trials. Conversations may be had regarding performance, pit times, and whether a two-tire or four-tire change is required.
The important thing is to recognize the importance of clear, effective communication, and the impact of unclear, emotionally charged language. It's not a panacea, but many of our timeworn feudal difficulties can be alleviated by some attention to the language that we use.