Added TestLocationVerifier to check for unit test location that also verifies package names and added it to the list of verifiers, a helper method to both PhaseUtils and FileUtils, a placeholder test for TestLocationVerifier.java, and moved verifiers and modifiers to their own subpackages.
One potential concern is code duplication with ProjectStructureVerifier. Both that class and TestLocationVerifier take in paths and verify that they are valid directories. The only difference is that TestLocationVerifier checks for package statements ( package dataaccess) and if it finds a missing package like test/java/service, then it scans the directory for any misnamed or unrecognized packages. As a result, both verifiers have similar warnings.
Added
TestLocationVerifierto check for unit test location that also verifies package names and added it to the list of verifiers, a helper method to both PhaseUtils and FileUtils, a placeholder test forTestLocationVerifier.java, and moved verifiers and modifiers to their own subpackages.Resolves issue https://github.com/softwareconstruction240/autograder/issues/362.
One potential concern is code duplication with
ProjectStructureVerifier. Both that class andTestLocationVerifiertake in paths and verify that they are valid directories. The only difference is thatTestLocationVerifierchecks for package statements (package dataaccess) and if it finds a missing package liketest/java/service, then it scans the directory for any misnamed or unrecognized packages. As a result, both verifiers have similar warnings.