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
{{ message }}
This repository has been archived by the owner on Oct 3, 2023. It is now read-only.
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.
The text was updated successfully, but these errors were encountered:
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
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
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.
The unit tests in
src/test
should reflect the package hierarchy insrc/main
. Currently, there are example models insrc/test/scala/modbat/{test,examples}
, but the unit tests that use them are insrc/test/scala/modbat/mbt
. They should be moved to the other two directories, and renamed if needed.The text was updated successfully, but these errors were encountered: