1767N/A<?
xml version="1.0" encoding="utf-8" ?>
1767N/A<
meta http-
equiv="Content-Type" content="text/html; charset=utf-8" />
1767N/A<
title>The VirtualBox Validation Kit</
title>
1767N/A:Author: David Goodger (goodger@python.org)
1767N/A:Copyright: This stylesheet has been placed in the public domain.
1767N/ADefault cascading style sheet for the HTML output of Docutils.
3996N/A/* used to remove borders from tables and images */
1767N/A The right padding separates the table cells. */
1767N/A padding: 0 0.5em 0 0 ! important }
1767N/A /* Override more specific margin styles with "! important". */
1767N/A margin-top: 0 ! important }
1767N/A margin-bottom: 0 ! important }
1767N/A/* Uncomment (and remove this text!) to get bold-faced definition list terms
font-family: sans-serif }
font-family: sans-serif }
/* Uncomment (and remove this text!) to get reduced vertical space in
background-color: #ffffee ;
font-family: sans-serif ;
/* reset inner alignment in figures */
list-style: lower-alpha }
list-style: upper-alpha }
list-style: lower-roman }
list-style: upper-roman }
font-family: sans-serif ;
font-family: sans-serif ;
pre.code .ln { color: grey; } /* line numbers */
pre.code, code { background-color: #eeeeee }
pre.code .comment, code .comment { color: #5C6576 }
pre.code .keyword, code .keyword { color: #3B0D06; font-weight: bold }
pre.code .deleted, code .deleted { background-color: #DEB0A1}
pre.code .inserted, code .inserted { background-color: #A3D289}
font-family: sans-serif ;
font-family: sans-serif ;
font-family: sans-serif }
/* font-size relative to parent (
h1..h6 element) */
border-left: solid 1px gray;
border-left: solid 1px black;
<
div class="document" id="the-virtualbox-test-suite">
<
h1 class="title">The VirtualBox Validation Kit</
h1>
<
div class="section" id="introduction">
<
p>The VirtualBox test suite is the new way we're doing automated testing of
VirtualBox and is still rather incomplete, in fact it will probably always be
incomplete as there will always be new features and guest OSes to test.</
p>
<
p>We're warmly welcoming contributions, new ideas for good tests, and fixes.</
p>
<
div class="section" id="directory-layout">
<
h1>Directory Layout</
h1>
<
dd><
p class="first">The documentation for the test suite mostly lives here, the exception being
readme.txt files that are better off living near what they concern.</
p>
<
p class="last">For a definition of terms used here, see the Definitions / Glossary section
<
dd><
p class="first">Python module implementing the base test drivers and supporting stuff.
API wrappers that makes things easier to use and glosses over a lot of API
doesn't necessarily have to be, it's up to the individual test driver.</
p>
<
p>For logging, reporting result, uploading useful files and such we have a
both local (for local testing) and remote (for testboxes + test manager)
<
p class="last">There is also a VBoxTXS client implementation in
txsclient.py and a stacked
use the TXS client indirectly thru
vbox.py methods. The installer driver
is a special trick for the testbox+testmanager setup.</
p>
<
dd>The python scripts driving the tests. These are organized by what they
test and are all derived from the base classes in /
testdriver (mostly from
vbox.py of course). Most tests use one or more VMs from a standard set of
though the installation tests used prepared ISOs and floppy images.</
dd>
<
dd>Text documents describing the preconfigured test VMs defined by
prepare installation ISOs when we get around to it (soon).</
dd>
<
dd><
p class="first">Test utilities and lower level test programs, compiled from C, C++ and
Assembly mostly. Generally available for both host and guest,
i.e. in the
of the more important utilities. It implements a remote execution service
for running
programs/
tests inside VMs and on other test boxes. See
<
p class="last">A simple network bandwidth and latency test program can be found in
<
dd><
p class="first">Boot sector test environment. This allows creating floppy images in
assembly that tests specific CPU or device behaviour. Most tests can be
put on a USB stick, floppy or similar and booted up on real hardware for
comparison. All floppy images can be used for manual testing by developers
and most will be used by test drivers (/
tests/<
em>/td</
em>.py) sooner or later.</
p>
<
p class="last">The boot sector environment is heavily bound to yasm and it's ability to
link binary images for single assembly input units. There is a "library"
of standard initialization code and runtime code, which include switch to
all (well V8086 mode is still missing, but we'll get that done eventually)
processor modes and paging modes. The image specific code is split into
init/
driver code and test template, the latter can be instantiated for each
process execution+paging mode.</
p>
<
dd>Python package containing common python code.</
dd>
<
dd>The testbox script. This is installed on testboxes used for automatic
testing with the testmanager.</
dd>
<
dd>The VirtualBox Test Manager (server side code). This is written in Python
and currently uses postgresql as database backend for no particular reason
other than that it was already installed on the server the test manager was
going to run on. It's relatively generic, though there are of course
things in there that are of more use when testing VirtualBox than other
things. A more detailed account (though perhaps a little dated) of the
<
dd>A start a local test result analysis, comparing network test output. We'll
probably be picking this up again later.</
dd>
<
dd>Various code snippets that may be turned into real tests at some point.</
dd>
<
table class="docutils field-list" frame="void" rules="none">
<
col class="field-name" />
<
col class="field-body" />
<
tr class="field"><
th class="field-name">Status:</
th><
td class="field-body">$Id$</
td>
<
tr class="field"><
th class="field-name">Copyright:</
th><
td class="field-body">Copyright (C) 2010-2014 Oracle Corporation.</
td>