2002-10-03 20:41:23 +00:00
|
|
|
<title>Testing BOINC</title>
|
2002-08-20 23:54:17 +00:00
|
|
|
<body bgcolor=ffffff>
|
2002-10-03 20:41:23 +00:00
|
|
|
<h2>Testing BOINC</h2>
|
2002-10-03 18:33:46 +00:00
|
|
|
|
2002-10-03 20:41:23 +00:00
|
|
|
<h3>1) PHP-based testing framework</h3>
|
|
|
|
|
|
|
|
|
|
doc/test.php is a library of PHP classes that make it easy to
|
2002-10-04 00:16:41 +00:00
|
|
|
write scripts that perform end-to-end tests of BOINC.
|
2002-10-03 20:41:23 +00:00
|
|
|
|
|
|
|
|
<h4>1.1) Goals of the testing framework</h4>
|
|
|
|
|
|
|
|
|
|
The goal of the framework is to support automated testing of BOINC itself,
|
|
|
|
|
and of BOINC applications.
|
|
|
|
|
Each test is performed by a PHP script that initializes
|
|
|
|
|
the system to a deterministic state, executes the system,
|
|
|
|
|
detects termination, and returns success or failure depending
|
|
|
|
|
on the final state.
|
|
|
|
|
<p>
|
|
|
|
|
Many BOINC features involve multiple projects and/or multiple hosts.
|
|
|
|
|
It would be prohibitively complex to do automated testing
|
|
|
|
|
on multiple physical hosts.
|
|
|
|
|
Fortunately the BOINC architecture makes it possible for
|
|
|
|
|
multiple projects and (virtual) hosts to reside on a single physical host.
|
|
|
|
|
So the testing framework uses this approach.
|
|
|
|
|
|
|
|
|
|
<p>
|
2002-10-04 00:16:41 +00:00
|
|
|
The framework lets you test systems with any of the following attributes:
|
2002-10-03 20:41:23 +00:00
|
|
|
<ul>
|
|
|
|
|
<li> Multiple projects
|
|
|
|
|
<li> Multiple applications per project
|
|
|
|
|
<li> Multiple participants per project
|
|
|
|
|
<li> Multiple hosts, with arbitrary enrollment in projects
|
|
|
|
|
</ul>
|
2002-10-04 00:16:41 +00:00
|
|
|
The following system attributes are planned but not implemented yet:
|
|
|
|
|
<ul>
|
|
|
|
|
<li> Multiple data servers or scheduling servers per project.
|
|
|
|
|
<li> Simulated failures of servers and network connections.
|
|
|
|
|
<li> Simulations of various host conditions
|
|
|
|
|
(out of disk space, crash/reboot, etc.).
|
|
|
|
|
</ul>
|
2002-10-03 20:41:23 +00:00
|
|
|
|
|
|
|
|
<h4>1.2) Directory structure</h4>
|
|
|
|
|
|
2002-10-04 00:16:41 +00:00
|
|
|
To use the testing framework,
|
|
|
|
|
you must designate a "BOINC projects" directory on your test host.
|
2002-10-03 20:41:23 +00:00
|
|
|
The framework will create subdirectories as follows:
|
|
|
|
|
<pre>
|
|
|
|
|
boinc_projects/
|
|
|
|
|
proj1/
|
|
|
|
|
cgi/
|
|
|
|
|
download/
|
|
|
|
|
html_ops/
|
|
|
|
|
html_user/
|
|
|
|
|
keys/
|
|
|
|
|
upload/
|
|
|
|
|
proj2/
|
|
|
|
|
...
|
|
|
|
|
</pre>
|
|
|
|
|
where proj1, proj2 etc. are the names of the projects in your scripts.
|
|
|
|
|
|
|
|
|
|
<p>
|
2002-10-04 00:16:41 +00:00
|
|
|
Similarly, you must designate a "BOINC hosts" directory on your test host.
|
2002-10-03 20:41:23 +00:00
|
|
|
The framework will create subdirectories as follows:
|
|
|
|
|
<pre>
|
|
|
|
|
boinc_hosts/
|
|
|
|
|
host1/
|
|
|
|
|
projects/
|
|
|
|
|
slots/
|
|
|
|
|
client_state.xml
|
|
|
|
|
log_flags.xml
|
|
|
|
|
host2/
|
|
|
|
|
...
|
|
|
|
|
</pre>
|
|
|
|
|
where host1, host2 etc. are the names of the hosts in your scripts.
|
|
|
|
|
|
|
|
|
|
<h4>1.3) Classes</h4>
|
|
|
|
|
|
|
|
|
|
The framework provides the following classes
|
|
|
|
|
<pre>
|
|
|
|
|
class Project { // represents a project
|
|
|
|
|
var $name; // defaults to "test"; override if needed
|
2002-10-04 00:16:41 +00:00
|
|
|
var $generate_keys; // set to true if you want to generate
|
|
|
|
|
// encryption keys for this project (slow)
|
2002-10-03 20:41:23 +00:00
|
|
|
function add_user($user); // add a User to project's DB
|
|
|
|
|
function add_app($app); // add an application
|
|
|
|
|
function add_app_version($app_version); // add an app version
|
|
|
|
|
function install(); // set up directories and DB
|
|
|
|
|
function start(); // start feeder
|
|
|
|
|
function stop(); // stop feeder
|
|
|
|
|
function compare_file($out, $correct); // verify that a result file
|
|
|
|
|
// matches a known-correct file
|
2002-10-06 00:43:55 +00:00
|
|
|
function check_results($n, $result); // check that there are n results
|
|
|
|
|
// and that they match "result"
|
|
|
|
|
// (for all fields that are defined)
|
2002-10-03 20:41:23 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
|
|
class User { // represents an account on a project
|
|
|
|
|
var $name; // override if needed
|
|
|
|
|
var $email_addr;
|
|
|
|
|
var $authenticator;
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
class Host { // represents a (virtual) host
|
|
|
|
|
function Host($user);
|
|
|
|
|
function add_project($project);
|
|
|
|
|
function install();
|
|
|
|
|
function run($flags);
|
2002-10-06 00:43:55 +00:00
|
|
|
function check_file_present($project, $name);
|
|
|
|
|
// check that a file exists
|
2002-10-03 20:41:23 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
|
|
class App { // represents an application
|
|
|
|
|
function App($name);
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
class App_Version { // represents an application version
|
|
|
|
|
var $version; // defaults to 1
|
|
|
|
|
var $exec_name; // name of executable; default to app name
|
|
|
|
|
function App_Version($app);
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
class Work { // represents a workunit and some results
|
|
|
|
|
var $wu_template; // name of workunit template file
|
|
|
|
|
var $result_template; // name of result template file
|
|
|
|
|
var $nresults; // number of results for this WU
|
|
|
|
|
var $input_files; // array of input file names
|
|
|
|
|
function Work($project, $app);
|
|
|
|
|
function install(); // install in DB and directories
|
|
|
|
|
}
|
|
|
|
|
</pre>
|
|
|
|
|
A test script instantiates one or more instances of
|
|
|
|
|
these classes, links them as needed,
|
|
|
|
|
installs them, starts the projects, runs the hosts.
|
|
|
|
|
It then checks the final state
|
|
|
|
|
(typically, that results are done and result files are correct).
|
|
|
|
|
|
|
|
|
|
<h4>1.4) Environment vars</h4>
|
|
|
|
|
|
|
|
|
|
Before using the test framework,
|
|
|
|
|
you must define the following environment variables
|
|
|
|
|
(example values are given - you must supply your own):
|
2002-10-03 18:33:46 +00:00
|
|
|
<pre>
|
|
|
|
|
setenv BOINC_PROJECTS_DIR /home/david/boinc_projects
|
2002-10-03 20:41:23 +00:00
|
|
|
# BOINC projects directory
|
2002-10-03 18:33:46 +00:00
|
|
|
setenv BOINC_HOSTS_DIR /home/david/boinc_hosts
|
2002-10-03 20:41:23 +00:00
|
|
|
# BOINC hosts directory
|
2002-10-03 18:33:46 +00:00
|
|
|
setenv BOINC_USER_NAME david
|
2002-10-04 00:16:41 +00:00
|
|
|
# part of DB name, and prepended to web error log entries
|
2002-10-03 18:33:46 +00:00
|
|
|
setenv BOINC_SRC_DIR /home/david/boinc_cvs/boinc
|
2002-10-03 20:41:23 +00:00
|
|
|
# BOINC source directory
|
2002-10-03 18:33:46 +00:00
|
|
|
setenv BOINC_CGI_DIR /home/david/cgi-bin
|
2002-10-03 20:41:23 +00:00
|
|
|
# path of a CGI directory
|
2002-10-03 18:33:46 +00:00
|
|
|
setenv BOINC_CGI_URL http://localhost/cgi-bin
|
2002-10-03 20:41:23 +00:00
|
|
|
# URL of that directory
|
2002-10-03 18:33:46 +00:00
|
|
|
setenv BOINC_HTML_DIR /home/david/html
|
2002-10-03 20:41:23 +00:00
|
|
|
# path of a web-page directory
|
2002-10-03 18:33:46 +00:00
|
|
|
setenv BOINC_HTML_URL http://localhost
|
2002-10-03 20:41:23 +00:00
|
|
|
# URL of that directory
|
2002-10-03 18:33:46 +00:00
|
|
|
setenv BOINC_KEY_DIR /home/david/boinc_keys
|
2002-10-03 20:41:23 +00:00
|
|
|
# path of some pre-generated security keys
|
2002-10-03 18:33:46 +00:00
|
|
|
setenv BOINC_PLATFORM i686-pc-linux-gnu
|
2002-10-03 20:41:23 +00:00
|
|
|
# platform name of this machine
|
2002-10-15 21:55:48 +00:00
|
|
|
setenv BOINC_SHMEM_KEY 0x3abc1234
|
|
|
|
|
# shared-memory key; must be less than 2^31
|
2002-10-03 18:33:46 +00:00
|
|
|
</pre>
|
2002-10-03 20:41:23 +00:00
|
|
|
<h4>1.5) Example script</h4>
|
|
|
|
|
|
|
|
|
|
The following script (test/test_uc.php)
|
|
|
|
|
illustrates the use of the testing framework.
|
|
|
|
|
<pre>
|
|
|
|
|
#! /usr/local/bin/php
|
|
|
|
|
<?php
|
|
|
|
|
include_once("test.inc");
|
|
|
|
|
|
|
|
|
|
$project = new Project;
|
|
|
|
|
$user = new User();
|
|
|
|
|
$host = new Host($user);
|
|
|
|
|
$app = new App("upper_case");
|
|
|
|
|
$app_version = new App_Version($app);
|
|
|
|
|
|
|
|
|
|
$project->add_user($user);
|
|
|
|
|
$project->add_app($app);
|
|
|
|
|
$project->add_app_version($app_version);
|
|
|
|
|
$project->install(); // must install projects before adding to hosts
|
|
|
|
|
|
2002-10-06 00:43:55 +00:00
|
|
|
$host->log_flags = "log_flags.xml";
|
2002-10-03 20:41:23 +00:00
|
|
|
$host->add_project($project);
|
|
|
|
|
$host->install();
|
|
|
|
|
|
|
|
|
|
echo "adding work\n";
|
|
|
|
|
|
2002-10-06 00:43:55 +00:00
|
|
|
$work = new Work($app);
|
2002-10-03 20:41:23 +00:00
|
|
|
$work->wu_template = "uc_wu";
|
|
|
|
|
$work->result_template = "uc_result";
|
|
|
|
|
$work->nresults = 2;
|
|
|
|
|
array_push($work->input_files, "input");
|
2002-10-06 00:43:55 +00:00
|
|
|
$work->install($project);
|
2002-10-03 20:41:23 +00:00
|
|
|
|
|
|
|
|
$project->start();
|
|
|
|
|
$host->run("-exit_when_idle");
|
|
|
|
|
$project->stop();
|
|
|
|
|
|
2002-10-06 00:43:55 +00:00
|
|
|
$result->state = RESULT_STATE_DONE;
|
|
|
|
|
$result->stderr_out = "APP: upper_case: starting, argc 1";
|
|
|
|
|
$result->exit_status = 0;
|
|
|
|
|
$project->check_results(2, $result);
|
2002-10-03 20:41:23 +00:00
|
|
|
$project->compare_file("uc_wu_0_0", "uc_correct_output");
|
|
|
|
|
$project->compare_file("uc_wu_1_0", "uc_correct_output");
|
|
|
|
|
?>
|
|
|
|
|
</pre>
|
|
|
|
|
|
|
|
|
|
<h4>1.6) Implementation</h4>
|
2002-10-04 00:16:41 +00:00
|
|
|
Project->Install() does the following:
|
|
|
|
|
<ul>
|
|
|
|
|
<li> Create the project directory and its subdirectories.
|
|
|
|
|
<li> Create encryption keys if needed.
|
|
|
|
|
<li> Create a database for this project,
|
|
|
|
|
named (BOINC_USER_NAME)_(project-name).
|
|
|
|
|
This is done by macro-substituting the database name
|
|
|
|
|
into db/drop.sql, db/schema.sql, and db/constraints.sql.
|
|
|
|
|
<li> Insert initial records in the project, platform, user, and app tables.
|
|
|
|
|
<li> Run tools/add to create app_version records,
|
|
|
|
|
to copy the application executables from the source directory
|
|
|
|
|
to the download directory, and to compute their digital signatures.
|
|
|
|
|
<li> Copy the server programs (cgi, feeder, file_upload_handler)
|
|
|
|
|
from the source directory to the project/cgi directory.
|
|
|
|
|
<li> Generate the configuration file (config.xml) used by
|
|
|
|
|
the server programs.
|
|
|
|
|
<li> Copy the user and administrative PHP files to the
|
|
|
|
|
project directories html_user and html_ops.
|
|
|
|
|
<li> Create a file "db_name" in project/html_user and project/html_ops.
|
|
|
|
|
<li> Macro-process html_user/index.html to insert the correct
|
|
|
|
|
scheduler URL.
|
|
|
|
|
<li> Create symbolic links (with the project name)
|
|
|
|
|
from the main HTML and CGI directories to the project directory.
|
|
|
|
|
</ul>
|
2002-10-03 20:41:23 +00:00
|
|
|
|
2002-10-04 00:16:41 +00:00
|
|
|
<p>
|
|
|
|
|
Host->install() does the following:
|
|
|
|
|
<ul>
|
|
|
|
|
<li> Delete and recreate the directory for this host.
|
|
|
|
|
<li> Create an account file (account_masterURL.xml) for
|
|
|
|
|
each project in which this host participates.
|
|
|
|
|
</ul>
|
2002-10-03 20:41:23 +00:00
|
|
|
<h3>2) Test applications</h3>
|
2002-04-30 22:22:54 +00:00
|
|
|
<p>
|
2002-08-19 18:43:10 +00:00
|
|
|
The <b>apps</b> directory contains the following test applications:
|
2002-04-30 22:22:54 +00:00
|
|
|
<ul>
|
2002-08-19 18:43:10 +00:00
|
|
|
<li>
|
|
|
|
|
<b>concat</b>: concatenates its input files.
|
|
|
|
|
Input and output filenames are passed on the command line.
|
|
|
|
|
<li>
|
|
|
|
|
<b>upper_case</b>: reads from stdin, converts to upper case,
|
2002-04-30 22:22:54 +00:00
|
|
|
writes to stdout.
|
2002-08-19 18:43:10 +00:00
|
|
|
<li>
|
|
|
|
|
<b>uc_slow</b>: like upper_case, but processes only one
|
|
|
|
|
character per second.
|
|
|
|
|
Checkpoints every 5 characters. Restartable.
|
2002-04-30 22:22:54 +00:00
|
|
|
</ul>
|
2002-10-03 20:41:23 +00:00
|
|
|
|
|
|
|
|
<h3>3) Test scripts</h3>
|
|
|
|
|
<p>
|
2002-07-29 19:01:38 +00:00
|
|
|
The <b>test</b> directory contains PHP scripts, together with XML
|
|
|
|
|
templates and sample input files, for initializing and testing the
|
|
|
|
|
entire system:
|
2002-04-30 22:22:54 +00:00
|
|
|
<ul>
|
2002-08-19 18:43:10 +00:00
|
|
|
<li>
|
|
|
|
|
<b>test_uc.php</b>: tests I/O connection using descriptors.
|
|
|
|
|
<li>
|
|
|
|
|
<b>test_concat.php</b>: tests I/O connection using command-line
|
2002-07-29 19:01:38 +00:00
|
|
|
args and filenames.
|
2002-08-19 18:43:10 +00:00
|
|
|
<li>
|
|
|
|
|
<b>test_uc_slow.php</b>: tests checkpoint/restart.
|
|
|
|
|
You have to run the client yourself, kill and restart it a few times.
|
|
|
|
|
<li>
|
|
|
|
|
<b>test_prefs.php</b>: tests some aspects of preferences.
|
|
|
|
|
<li>
|
|
|
|
|
<b>test_api.php</b>: tests to ensure the api is working properly.
|
|
|
|
|
<li>
|
|
|
|
|
<b>test_water.php</b>: tests some aspects of water marks.
|
|
|
|
|
<li>
|
|
|
|
|
<b>test_rsc.php</b>: tests that scheduling server only sends
|
2002-10-03 20:41:23 +00:00
|
|
|
feasible work units.
|
2002-04-30 22:22:54 +00:00
|
|
|
</ul>
|
