Since, if you look at the output when make test is run, all files in module/t. are run in directory listing order, why not take advantage of that - as I and a good number of others do. This is done by prefixing the test files (i.e. t/*.t) with a number e.g.

t/00_base.t
t/01_base+1.t
.
.
[download]

etc. etc. - or in your case

t/00_perf1.t
t/01_perf1.t
t/02_perf2.t
.
.
/C>
or maybe even more meaningful names (to you) than <c>nn_perfnn.t
[download]

You will undoubtedly find perl testing - A developers notebook to be of great use (it's where I had the above idea confirmed by far more knowledgeable others).

Update:

Added afterthought/post-script ... which should have been the first thought!!