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
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+7-1Lines changed: 7 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -24,7 +24,13 @@ gpublish HELP_functionName
24
24
This will "publish" the documentation in the form of HTML files in the `GIBBON/docs/html` folder. The content there will then be automatically added to, and rendered on, the website when the website is updated.
25
25
26
26
## Testing
27
-
For the moment the DEMO_ and HELP_ files may serves as a test suite. The `testGibbon` function can be used to run (and "publish" HTML if needed) these tests/demos automatically.
27
+
28
+
New code should define well-structured [unit tests](https://www.mathworks.com/help/matlab/matlab_prog/ways-to-write-unit-tests.html), stored in the `tests` directory and labeled `TEST_functionName.m`. These will
29
+
be picked up by our CI pipeline and run on a remote GitHub runner, so make sure to keep your tests small and portable.
30
+
31
+
If you are new to unit tests, the examples `functionTestTemplate` and `ClassTestTemplate` might be a good starting point.
32
+
33
+
Unfortunately, the bulk of the code does not yet have structured tests. The `DEMO_*` and `HELP_*` files may serve as a more extensive test suite. The `testGibbon` function can be used to run (and "publish" HTML if needed) these tests/demos automatically.
28
34
29
35
## Pull requests
30
36
- Try not to pollute your pull request with unintended changes – keep them simple and small. If possible, squash your commits.
0 commit comments