I don't think tests can be (easily) set up to be tested by other tests

To test a test requires replacing what the test is testing with the test-tester.

For tests that call a function in the app or module being tested, the called function would be replaced a "stub" function that does 2 main things: Check and log the supplied inputs, then return a result. The result could be completely random, randomly chosen from a list or the next in sequence (which would require the test-tester preserve it's current state).

For tests, like the above, where the tests are "driving" the testing, it will be necessary to run the test-under-test enough times to insure full coverage of the test-under-test.

For test where the app or module under test is driving the testing, test-tester will be able to perform the test as many ties as needed.