-
-
Notifications
You must be signed in to change notification settings - Fork 346
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
Better Modularity for TESTS / Unification of test packages #16607
Comments
Here is the list:
|
This was referenced May 13, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We should follow the simple guideline that TESTS should be separated from RUNTIME code. Because when you want to have a modular and minimal system you might only want to use packages with the RUNTIME code and only load/use the tests during development phase.
This is easily achieved by packaging the test classes into an own separate package.
Now we have many tests in Pharo and the typical pattern is to package them into a separate package with the additional extension "-Tests". So if you have an application like "MyKillerApp" you might have
MyKillerApp-Core
MyKillerApp-UI
with either
MyKillerApp-Core-Tests
MyKillerApp-UI-Tests
or a common
MyKillerApp-Tests
package.
Unfortunately not all test classes follow that best practice and we have 64 violations of this simple rule:
which gives 64 viiolations in Pharo 13.
We should clean them and add a release test so the test classes are properly packaged.
The text was updated successfully, but these errors were encountered: