mirror of
https://gitlab.gnome.org/GNOME/glib.git
synced 2025-08-02 07:23:41 +02:00
docs: Mention how to run the test suite in CONTRIBUTING.md
We don’t want `CONTRIBUTING.md` to become an exhaustive manual of how to contribute to what is a fairly standard C project using Meson, but it is a fairly helpful hint to mention how to run the test suite. Then people can use `meson test --help` and the Meson documentation to learn more. Pointed out on !4589. Signed-off-by: Philip Withnall <pwithnall@gnome.org>
This commit is contained in:
@@ -153,7 +153,15 @@ Typically, you should work on your own branch:
|
||||
$ git checkout -b your-branch
|
||||
```
|
||||
|
||||
Once you’ve finished working on the bug fix or feature, push the branch
|
||||
Once you’ve finished working on the bug fix or feature, make sure the tests
|
||||
pass by using the standard `meson` test harness:
|
||||
|
||||
```sh
|
||||
$ meson test -C _builddir
|
||||
$ meson test -C _builddir --setup=valgrind
|
||||
```
|
||||
|
||||
Then push the branch
|
||||
to the Git repository and open a new merge request, to let the GLib
|
||||
core developers review your contribution.
|
||||
|
||||
|
Reference in New Issue
Block a user