ruby on rails - How to ensure that rspec UI tests for existing functionality use the same approach and tools as BDD/TDD -

this common theme have seen in many organizations - how quality assurance and/or user experience folks write ui automation tests large portions of untested functionality, , how ensure approach , tools used writing ui tests existing (but untested) functionality use same approach , tools feature specs being written test , behavior driven tests.

how can qe, ux , developers develop these tests without clashing in approach , style? tools, processes or communications work in reality. approaches people on same page despite different backgrounds, skills , passions.

my context web application written in ruby on rails.