Difference between revisions of "ZDTM API"

From CRIU
Jump to navigation Jump to search
Line 1: Line 1:
 
This page describes the API one ''should'' use to write new test in ZDTM.
 
This page describes the API one ''should'' use to write new test in ZDTM.
 +
 +
== API for test itself ==
 +
 +
The test should clearly describe 3 stages:
 +
 +
; Preparations
 +
: These are actions that test does before the process(es) get checkpointed
 +
 +
;Actions
 +
: During this the process(es) will be interrupted at arbitrary place and get dumped
 +
 +
;Checks
 +
: After restore test should verify whether everything is OK or not
 +
 +
From the code perspective this looks like this:
 +
 +
<code>
 +
int main(int argc, char **argv)
 +
{
 +
test_init(argc, argv);
 +
 +
/* preparations */
 +
 +
test_daemon();
 +
 +
/* actions */
 +
 +
test_waitsig();
 +
 +
/* checks */
 +
 +
return 0;
 +
}
 +
</code>
 +
 +
== Adding test to automatic suite ==
  
 
[[Category: Development]]
 
[[Category: Development]]

Revision as of 16:02, 23 January 2015

This page describes the API one should use to write new test in ZDTM.

API for test itself

The test should clearly describe 3 stages:

Preparations
These are actions that test does before the process(es) get checkpointed
Actions
During this the process(es) will be interrupted at arbitrary place and get dumped
Checks
After restore test should verify whether everything is OK or not

From the code perspective this looks like this:

int main(int argc, char **argv) { test_init(argc, argv);

/* preparations */

test_daemon();

/* actions */

test_waitsig();

/* checks */

return 0; }

Adding test to automatic suite