<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.1.2//EN" "http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd" [
  <!ENTITY doctitle "GTEE User Manual">
  <!ENTITY docversion "0.0.1">
  <!ENTITY UTE "GTEE">
]>

<sect1 id="ute_concepts">
  <title>Concepts</title>
    <para>
      <emphasis>Test harness</emphasis> is a tool to run tests. Different test harnesses have different capabilities,
      setup and actual way of execution. Examples of test harness include Tonga, JavaTest, jtreg and others.
    </para>
    <para>
      <emphasis>Testbase</emphasis> (sometimes referred to as <emphasis>workspace</emphasis>) is a collection of tests. Testbase
      is usually located inside particular directory on file system (referred as <emphasis>testbase location</emphasis>). Testbase
      is executed with particular test harness.  Examples of testbase include VM Testbase, other SQE Testbases, JCK Runtime 6
      (or other version), JDK or HotSpot regression tests.
    </para>
    <para>
      <emphasis>Test component</emphasis> identifies class of testing that is performed. Among the examples are SQE functional
      components (<code>vm, jmx, swing,</code> etc.), <code>jck, javase</code> (tests from JavaSE workspace), <code>bigapps.</code>
      For UTE, normally test component has only informational value and no impact on functionality (<code>tonga</code>
      and <code>dtonga</code> are notable exceptions).
    </para>
    <para>
      <emphasis>Product</emphasis> is the program being tested (for example JDK 6u10 b26).
    </para>
    <para>
      <emphasis>Testrun</emphasis> is a particular execution of tests.
    </para>
    <para>
      <emphasis>Configuration</emphasis> of testrun may include several <emphasis>parameters,</emphasis> for example,
      particular product, product command-line options, harness module, testbase, test options or configuration, test lists
      or suites, other required entities (such as browsers and plugins).
    </para>
    <para>
      <emphasis>Harness module</emphasis> is a part of UTE which allows to run testing in a particular way with particular harness.
      In this manual, harness module is sometimes simply referred as harness. During testrun, one particular harness module is used.
    </para>
    <para>
      <emphasis>Result directory</emphasis> is the directory where data related to testrun is stored. It usually contains
      test results, configuration files, intermidiate data files and scripts, testrun and test log files.
    </para>
</sect1>
