Initialize the GLib testing framework, e.
g. by seeding the test random number generator, the name for get_prgname and parsing test related command line args.
So far, the following arguments are understood:
`perf`: Performance tests, may take long and report results (off by default).
`slow`, `thorough`: Slow and thorough tests, may take quite long and maximize coverage (off by default).
`quick`: Quick tests, should run really quickly and give good coverage (the default).
`undefined`: Tests for undefined behaviour, may provoke programming errors under trap_subprocess or expect_message to check that appropriate assertions or warnings are given (the default).
`no-undefined`: Avoid tests for undefined behaviour
Options which can be passed to ...
are:
g_set_user_dirs
to set XDG directories to point into that temporary directory for the duration of the unit test. See the
documentation for g_test_option_isolate_dirs.Since 2.58, if tests are compiled with `G_DISABLE_ASSERT` defined, init will print an error and exit. This is to prevent no-op tests from being executed, as assert is commonly (erroneously) used in unit tests, and is a no-op when compiled with `G_DISABLE_ASSERT`. Ensure your tests are compiled without `G_DISABLE_ASSERT` defined.
Example: Test, initialization:
public static int main (string[] args) {
// Use ./test --help to review our options
Test.init (ref args);
// Register test cases via Test.add_func & friends
Test.run ();
return 0;
}
valac --pkg glib-2.0 GLib.Test.init.vala
... |
null-terminated list of special options, documented below. |
argc |
Address of the |
argv |
Address of the |