shaba/systemd
1
0
Fork 0
mirror of https://github.com/systemd/systemd.git synced 2024-12-22 17:35:35 +03:00
Code

HACKING: add a short description of new unit tests

Browse Source 
This is all "should" and "encouraged", since we are not strict with
this, for better or worse.
This commit is contained in:
Zbigniew Jędrzejewski-Szmek 2017-11-04 21:02:35 +01:00
parent 78733a523a
commit 8f8dc208be
1 changed files with 9 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
HACKING
View File

@ -11,6 +11,15 @@ CODING_STYLE for details. Also have a look at our Contribution Guidelines:
https://github.com/systemd/systemd/blob/master/.github/CONTRIBUTING.md https://github.com/systemd/systemd/blob/master/.github/CONTRIBUTING.md
When adding new functionality, tests should be added. For shared functionality
(in src/basic and src/shared) unit tests should be sufficient. The general
policy is to keep tests in matching files underneath src/test,
e.g. src/test/test-path-util.c contains tests for any functions in
src/basic/path-util.c. If adding a new source file, consider adding a matching
test executable. For features at a higher level, tests in src/test/ are very
strongly recommended. If that is no possible, integration tests in test/ are
encouraged.
Please always test your work before submitting a PR. For many of the components Please always test your work before submitting a PR. For many of the components
of systemd testing is straight-forward as you can simply compile systemd and of systemd testing is straight-forward as you can simply compile systemd and
run the relevant tool from the build directory. run the relevant tool from the build directory.