One simple way I used for a project had a special script that knew about test ordering as well as group ordering. Basically, this was set up in the __DATA__ section of the test script something like...

#testname      testgroup
base.t         core
dvd_core.t     core
dvd_mount.t    dvdread
dvd_read.t     dvdread
dvd_burn.t     dvdwrite
tape_core.t    core
tape_mount.t   taperead
tape_read.t    taperead
tape_write.t   tapewrite
[download]

This described the test order (from top to bottom) and the test group name. The user would invoke the script like "test.pl taperead" (or via make) which would run the non-hardware tests ("core") and then test mounting and reading (but not writing) a tape. That way I could just run the tests I wanted (some were very time consuming) and I didn't have to put checks in the various scripts for hardware existence and mess with embedding Test::More SKIP sections everywhere. Obviously you can get sophisticated here wrt groupings, but it's pretty easy to set up a basic group dependency list with a hash.