You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@ElladeLore has mentioned that JUnit tests need to be in a file that has the name of the class being tested (e.g. A needs to be tested by ATest). For small classes I sometimes bundle them together so classes X, Y and Z are tested by WTest.
Is there any particular reason for constraining test classes so that they need to match the name of the class being tested? (Aside from JUnit conventions?)
The text was updated successfully, but these errors were encountered:
So because of the way tests are run independently where their file is run with all the other files from the sample solution we need to have a way to map the test files to the file that should be subbed in
Probably better ways but I leave you in the capable hands of our dear Evan 🤒
@ElladeLore has mentioned that JUnit tests need to be in a file that has the name of the class being tested (e.g. A needs to be tested by ATest). For small classes I sometimes bundle them together so classes X, Y and Z are tested by WTest.
Is there any particular reason for constraining test classes so that they need to match the name of the class being tested? (Aside from JUnit conventions?)
The text was updated successfully, but these errors were encountered: