I know RPMs can have build dependencies, but can they also have testing dependencies?

At work we are developing a number of different software tools in different repositories, which get packaged as RPM files. Our suite of test data for unit and integration testing has now grown to the gigabytes, and rather than bodily import that into every RPM, we would like to have a dependency that is only triggered when performing tests. That is, some of our testers will not need the test-data repository. They will update the code repository, run rpmbuild --nocheck, and test the result by hand (such as user-interface testing, which we haven't automated). Other folks in QA will download the code repository, run 'rpmbuild' and should be told if their installed test-data RPM is sufficiently recent or not. For our production build robot, we want it to be able to examine the dependencies, download any needed updates, run all tests, and package the final output for shipment. Is this even possible? The RPM specs I can find say almost nothing about testing environments, or use of %check.