Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
THe source code of my the legacy application I am maintaining is in many folders and subfolders.
I am starting creating unittests as a base for refactoring.
Do you suggest I put all tests in a single place or for every folder of code i create a subfolder called \FolderNameTests ?
Or do you have other suggestions?
I think it makes sense to have a src folder for your source, and a tests folder for your tests, and the the directory structure under test should match the directory structure under source.
For Java, where packages affect member visibility, this is particularly important, because the directory structure reflects the packages. So not following the convention will mean you might not be able to test protected/default visibility scoped methods.