Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

JUnit Test Naming #27

Open
applebyter opened this issue Apr 6, 2020 · 2 comments
Open

JUnit Test Naming #27

applebyter opened this issue Apr 6, 2020 · 2 comments
Assignees
Labels
question Further information is requested

Comments

@applebyter
Copy link
Collaborator

@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?)

@applebyter applebyter added the question Further information is requested label Apr 6, 2020
@wisebaldone
Copy link
Collaborator

Crashes without it because Brae doesnt know what he is doing

@wisebaldone wisebaldone self-assigned this Apr 6, 2020
@BraeWebb
Copy link
Owner

BraeWebb commented Apr 6, 2020

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 🤒

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

3 participants