Closed chrisallenlane closed 11 years ago
This is going to be hard to do because of the number of layers of technology that are woven together to make everything (when you include the functionality of the trojans themselves within the scope of testing, at least.) With that said, it makes sense to try to split testing effort between the wash client itself and the various trojan/payload combinations that are possible. Testing the easy/obvious client-side-only functionality of the wash console itself might be a good starting point.
Unit tests have been written, though code-coverage is still somewhat poor. Because these can be improved forever, though, I'm going to rename the ticket to "Improve Unit Tests" (from "Write Unit Tests") and set the priority to "Icebox". Now that this minimal baseline has been established at least, I'll just chip away at this from time to time going forward.
Since this will be ongoing forever, I'm closing this ticket to cut down on the noise in the issue tracker.
Unit tests have now been written, but code coverage is poor. Work to improve the quality of the unit tests.