Description of problem: Submitting a test (make bkradd) is a process completely independent on presence of the test in cvs. While this may be handy from time to time, it hurts the maintainability. The version of the test in Beaker should be the same as in cvs. If for some reason there is a need to submit different version of the test, it has to be an explicit process, the special version should not "overwrite" the version tied to cvs and it should be marked appropriately.
I don't know how this would be done since tests can be written outside of Red Hat. What you are talking about is policy. Policy should be implemented by documentation and education.