Skip to content
This repository has been archived by the owner on Oct 3, 2023. It is now read-only.

Generated unit tests should use same package names as the parts they test #65

Closed
cyrille-artho opened this issue Jun 4, 2019 · 2 comments

Comments

@cyrille-artho
Copy link
Owner

The unit tests in src/test should reflect the package hierarchy in src/main. Currently, there are example models in src/test/scala/modbat/{test,examples}, but the unit tests that use them are in src/test/scala/modbat/mbt. They should be moved to the other two directories, and renamed if needed.

@cyrille-artho
Copy link
Owner Author

Probably the best approach is to do examples semi-manually, by looking at which files go there, and do the rest at the end in one bunch (they all go to src/test/scala/modbat/test).

@cyrille-artho cyrille-artho changed the title Generated unit tests should use same package names as parts they test Generated unit tests should use same package names as the parts they test Jun 4, 2019
@cyrille-artho
Copy link
Owner Author

Decided to keep the package names, as the separation into test and examples is a bit arbitrary from a testing point of view (the separation is only for documentation/distribution), and there is in fact no package modbat.test or modbat.examples in the main code; the main functionality is in modbat.mbt.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant