Staff provided test architecture

The staff provided classes in ps6.test are confusing me. Here are some of the issues:
1. It appears that PS6TestCase has a blatant error. It may try to access modeToTest[2] (when the array only has two elements) in its constructor.
2. What is the purpose of the PS6TestCase::testTextUI method? Why is it auto-fail and marked TODO? Can we not just use the PublicTextUITest class to test the text UI?
3. One test case in PublicProgADTTest causes an IllegalStateException in PS6TestCase (it can't handle invalid directions type errors). Is this supposed to happen? i.e. are we supposed to implement more functionality into PS6TestCase?

When I say "use [some staff provided entity]" above, I mean, "add more of our own tests to [the entity] and use it."

In addition, the suggestion in Pset "To use our testing infrastructure, you can model TestMapQuick after PublicTest. Then, create a class that stores your test queries similar to ValidateQueries (or make it an inner class in TestMapQuick) for both your programmatic interface and the text user interface. Add your test cases by creating appropriate TestRecords." doesn't make much sense since it refers to classes that I can't find.