Despite aggregating some common classes (namely TestResult and TestState), the UnitTest and StyleChecker (shouldn't this be StyleTest for consistency?) classes are currently packaged separately, while the interface Tester is packaged in models. Since these classes fulfill very similar functions (hence the interface) and aggregate a few common objects, unifying the entire testing functionality under a testing package and modifying TestResult to accommodate style checks seems logical. Since this is a pretty substantial design change, I decided to open an issue before changing the arrangement.
Despite aggregating some common classes (namely
TestResult
andTestState
), theUnitTest
andStyleChecker
(shouldn't this beStyleTest
for consistency?) classes are currently packaged separately, while the interfaceTester
is packaged inmodels
. Since these classes fulfill very similar functions (hence the interface) and aggregate a few common objects, unifying the entire testing functionality under atesting
package and modifyingTestResult
to accommodate style checks seems logical. Since this is a pretty substantial design change, I decided to open an issue before changing the arrangement.