Difference between revisions of "ZDTM test suite"

From CRIU
Jump to: navigation, search
(crtools -> criu)
m (add a bit more information)
Line 4: Line 4:
  
 
== Running ==
 
== Running ==
 +
=== All zdtm tests ===
 +
You can run all the tests by:
 +
      make test
 +
or by:
 +
      test/zdtm.sh
 +
Note, that if one test fails, ztdm will continue to run others. So, be sure to check its output for error messages.
  
You can run the tests manually by issuing a <code>make <testname>.pid</code> command. After you've done c/r-ing it you should run <code>make <testname>.out</code> and check for the <testname>.out file contents.
+
=== Certain test ===
 +
You can also run the tests manually by issuing a
 +
      make <testname>.pid
 +
command. After you've done c/r-ing it you should run  
 +
      make <testname>.out
 +
and check for the <testname>.out file contents.
  
 
If you don't want to mess with this you can use the <code>zdtm.sh</code> script. When launched without arguments runs all the tests one-by-one. The exact test can be specified by the command line argument. The <code>-l</code> option lists the tests it can run.
 
If you don't want to mess with this you can use the <code>zdtm.sh</code> script. When launched without arguments runs all the tests one-by-one. The exact test can be specified by the command line argument. The <code>-l</code> option lists the tests it can run.
  
 
[[Category:Development]]
 
[[Category:Development]]

Revision as of 12:23, 2 September 2014

Description

ZDTM stands for zero-down-time-migration. It's test suite developed for testing how OpenVZ live migration works. We use this test suite for checking how criu do their job. The suit consists of many small atomic tests -- each puts a process into some "state" (opens a file, maps a memory segment, puts data in a pipe, etc.), then asks to be checkpointed and restored. The in checks that the "state" was preserved (file is still open, memory is still mapped, pipe contains what was put into it).

Running

All zdtm tests

You can run all the tests by:

      make test

or by:

      test/zdtm.sh

Note, that if one test fails, ztdm will continue to run others. So, be sure to check its output for error messages.

Certain test

You can also run the tests manually by issuing a

      make <testname>.pid

command. After you've done c/r-ing it you should run

      make <testname>.out

and check for the <testname>.out file contents.

If you don't want to mess with this you can use the zdtm.sh script. When launched without arguments runs all the tests one-by-one. The exact test can be specified by the command line argument. The -l option lists the tests it can run.