search for: run_one_test

Displaying 15 results from an estimated 15 matches for "run_one_test".

2014 Oct 21
3
Re: [PATCH v5 1/7] tests: Introduce test harness for running tests.
...s/phony-guests") 0o755 > + with Unix_error _ -> ()); > + home // ".cache/libguestfs-tests/phony-guests" > + ) in Would it be possible to use use $XDG_CACHE_HOME if available, falling back to $HOME/.cache if not? > + (* Run a single test. *) > + and run_one_test dir test args = > + let skip_env = try Sys.getenv (skip_name test) with Not_found -> "" in > + if skip_env = "1" then ( > + printf "SKIP: %s\n%!" test; > + (1, 0, 0, 0, 1) > + ) > + else ( > + set_up_environment (); &g...
2014 Oct 24
0
Re: [PATCH v5 1/7] tests: Introduce test harness for running tests.
...can be specified multiple times) I suspect that encoding all this as options is going to be tedious, considering people can just set the associated environment variables instead. Could drop the --direct option for the same reason. > > + (* Run a single test. *) > > + and run_one_test dir test args = > > + let skip_env = try Sys.getenv (skip_name test) with Not_found -> "" in > > + if skip_env = "1" then ( > > + printf "SKIP: %s\n%!" test; > > + (1, 0, 0, 0, 1) > > + ) > > + else ( > &g...
2014 Sep 20
3
[PATCH v2 0/3] tests: Introduce test harness for running tests.
This has got to the stage where it actually works, both for running the tests in-tree and installed. The 'test-harness' script has become rather over-complex in the process however. Rich.
2014 Oct 05
0
[PATCH v5 1/7] tests: Introduce test harness for running tests.
...ests in a single directory. 'dir' is the + * directory name, and we are chdir'd into this directory + * already. + *) + and run_dir_tests dir tests = + let results = null_results in + let accumulate = + List.fold_left + (fun results t -> add_results results (run_one_test dir t [])) + in + let results = + if fast then accumulate results tests.check_fast + else results in + let results = + if normal then accumulate results tests.check + else results in + let results = + if slow then accumulate results tests.check_slow + else...
2015 Aug 06
0
[PATCH v4 01/17] tests: Introduce test harness for running tests.
...ests in a single directory. 'dir' is the + * directory name, and we are chdir'd into this directory + * already. + *) + and run_dir_tests dir tests = + let results = null_results in + let accumulate = + List.fold_left + (fun results t -> add_results results (run_one_test dir t [])) + in + let results = + if fast then accumulate results tests.check_fast + else results in + let results = + if normal then accumulate results tests.check + else results in + let results = + if slow then accumulate results tests.check_slow + else...
2014 Oct 03
0
[PATCH v3] tests: Introduce test harness for running tests.
...of the tests in a single directory. 'dir' is the + * directory name, and we are chdir'd into this directory + * already. + *) + and run_dir_tests dir tests = + let results = null_results in + let accumulate = + List.fold_left (fun results t -> add_results results (run_one_test dir t)) + in + let results = + if fast then accumulate results tests.check_fast + else results in + let results = + if normal then accumulate results tests.check + else results in + let results = + if slow then accumulate results tests.check_slow + else res...
2014 Sep 16
5
[PATCH 0/3] tests: Introduce test harness for running tests.
These are my thoughts on adding a test harness to run tests instead of using automake. The aim of this exercise is to allow us to run the full test suite on an installed copy of libguestfs. Another aim is to allow us to work around all the limitations and problems of automake. The first patch makes an observation that since the ./run script sets up $PATH to contain all the directories
2014 Oct 05
12
[PATCH v5 0/7] tests: Introduce test harness for running tests.
Since v4: - More tests have been converted. - Testing local guests fixed. - Drop no-exec-stack test.
2015 Aug 06
20
[PATCH v4 00/17] tests: Introduce test harness for running tests.
Since v3: - A large number of fixes, especially for running the tests on installed libguestfs. - Fixed EXTRA_DIST rules throughout. - Extra patch 17/17 which is a tidy-up of the generated XML listing guests. Rich.
2014 Oct 23
10
[PATCH v6 00/10] tests: Introduce test harness for running tests.
For v6: This is mainly just a rebase, but I have also added tests in the ocaml/ language bindings directory, and for all the OCaml-written virt tools. Rich.
2014 Oct 24
10
[PATCH v7 00/10] tests: Introduce test harness for running tests.
v7: The only changes since v6 are those suggested by Pino in the review of v5.
2015 Jul 28
10
[PATCH 00/10] tests: Introduce test harness for running tests.
I should probably start by saying this patch series isn't ready for review yet. This patch series adds a test harness to libguestfs. It allows us to run the tests outside the ordinary 'make check' path in the build tree. In particular, you can use this to run tests when libguestfs has been installed. 'make check' and the other 'make check-*' rules still work. The
2014 Oct 04
4
[PATCH v4 0/4] tests: Introduce test harness for running tests.
This converts more of the tests (basically everything under tests/) to use the test harness, revealing some problems which have subsequently been fixed. Rich.
2015 Jul 31
14
[PATCH v2 00/14] tests: Introduce test harness for running tests.
This is a more complete patch to add the test harness. The only parts missing now are the language bindings (except OCaml). The language bindings need a bit more thought. At the moment most language binding tests are done through some sort of shell script like perl/run-perl-tests which either runs each test itself or uses some language-specific machinary to run each test. The problem with that
2015 Aug 04
16
[PATCH v3 01/16] tests: Introduce test harness for running tests.
Since v2: - Add perl tests. - Reworked and fixed the tests for virt-builder. - Some further minor bug fixes.