-
-
Notifications
You must be signed in to change notification settings - Fork 3k
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
fixup processing parameters tests #2541
Changes from all commits
7ce35d1
222539f
2ce3c84
a7da531
6c34c72
879a598
27379df
b4346ad
a9a24cc
60e6b32
685ecca
b1d401a
2c08fcf
d9a289b
1715064
37e4f72
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -7,8 +7,10 @@ ADD_SUBDIRECTORY(images) | |
ADD_SUBDIRECTORY(modeler) | ||
ADD_SUBDIRECTORY(script) | ||
ADD_SUBDIRECTORY(tools) | ||
ADD_SUBDIRECTORY(tests) | ||
ADD_SUBDIRECTORY(ui) | ||
IF (ENABLE_TESTS) | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. So you propose to keep plugin tests in their directories? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Right - my reasoning is kind of abstract, so bear with me... Firstly, from a software patterns POV, "plugins" should be self contained. One small example of this is that moving plugins in and out of core is simpler if the plugin carries and installs it's own tests. And more abstractly, I've been thinking of plugins as python modules. Even though they aren't all currently built this way, I think we should move towards that. We're using python and the standard unit of application composition in Python is a module. The tests are part of the module and "/tests or /tests.py" is a standard place to store a modules tests. Finally, I think core plugins should serve as an example for contributed plugins, and they should resemble contributed plugins as much as possible so that in core plugins we're dogfooding the same plugin tooling and practices that we want contributors to use. To my point - part of the plugin code is (or should be) tests, and I hope we can move more contributors to write tests for their plugin by making it easy to run plugin tests in situ. This plugin doesn't solve that, but I think moving Processing's tests out of its module would be a step in the wrong direction. |
||
ADD_SUBDIRECTORY(tests) | ||
ENDIF (ENABLE_TESTS) | ||
|
||
FILE(GLOB OTHER_FILES metadata.txt) | ||
FILE(GLOB PY_FILES *.py) | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Isn't that installed via apt already?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
apt on osx? ;)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oops :)