702cdb35db
* test-suite/standalone/test-out-of-memory: Prevent the test harness from being inlined. If the test harness is inlined, it might cause the optimizer to omit the allocations being tested! |
||
|---|---|---|
| .. | ||
| .gitignore | ||
| Makefile.am | ||
| README | ||
| test-asmobs | ||
| test-asmobs-lib.c | ||
| test-bad-identifiers | ||
| test-command-line-encoding | ||
| test-command-line-encoding2 | ||
| test-conversion.c | ||
| test-extensions | ||
| test-extensions-lib.c | ||
| test-fast-slot-ref.in | ||
| test-ffi | ||
| test-ffi-lib.c | ||
| test-foreign-object-c.c | ||
| test-foreign-object-scm | ||
| test-guild-compile | ||
| test-guile-snarf | ||
| test-import-order | ||
| test-import-order-a.scm | ||
| test-import-order-b.scm | ||
| test-import-order-c.scm | ||
| test-import-order-d.scm | ||
| test-language | ||
| test-language.el | ||
| test-language.js | ||
| test-list.c | ||
| test-loose-ends.c | ||
| test-mb-regexp | ||
| test-num2integral.c | ||
| test-out-of-memory | ||
| test-pthread-create-secondary.c | ||
| test-pthread-create.c | ||
| test-require-extension | ||
| test-round.c | ||
| test-scm-c-bind-keyword-arguments.c | ||
| test-scm-c-read.c | ||
| test-scm-spawn-thread.c | ||
| test-scm-take-locale-symbol.c | ||
| test-scm-take-u8vector.c | ||
| test-scm-to-latin1-string.c | ||
| test-scm-values.c | ||
| test-scm-with-guile.c | ||
| test-smob-mark-race.c | ||
| test-smob-mark.c | ||
| test-srfi-4.c | ||
| test-stack-overflow | ||
| test-system-cmds | ||
| test-unwind.c | ||
| test-use-srfi.in | ||
| test-with-guile-module.c | ||
-*-text-*- These tests use the standard automake TESTS mechanism. Tests should be listed in TESTS in Makefile.am, and should exit with 0 on success, non-zero on failure, and 77 if the result should be ignored. See the automake info pages for more information. If you want to use a scheme script, prefix it as follows: #!/bin/sh exec guile -s "$0" "$@" !# Makefile.am will arrange for all tests (scripts or executables) to be run under uninstalled-env so that the PATH, LD_LIBRARY_PATH, and GUILE_LOAD_PATH will be augmented appropriately. The Makefile.am has an example of creating a shared library to be used from a test scheme script as well. You can also create standalone executables that include your own code, are linked against libguile, and that run a given test script (or scripts). One way to do this is to create the binary, make sure it calls scm_shell (argc, argv) as its final action, and put this bit at the top of your test script: #!./my-test-binary -s !#