<?php $theTab=3; ?>
<?php require_once('ietvert/theHeader.php'); ?>
<?php // require_once('Connections/DatuConnect.php'); ?>
<?php require_once('ietvert/theFunctions.php'); ?>
</head>
<?php
    /*** turn off error reporting ***/
/** ini_set('display_errors', 0); **/
?>

<body>

<div id="container">

<?php require_once('ietvert/pageHeader.php'); ?>
 
<div class="col810">
<div class="col624 borderSETSLightGreen">

  <div id="content">

  <p class="breadcrumb"> <span>You are here: </span> <a href="index.php">Home</a>&nbsp; &raquo; <a href="products.php">Products</a>&nbsp; &raquo; SETSTTesting</p>
  <hr />
  <img src="images/SETSTTestingLogo.jpg" width="200" height="82" alt="SETSTTestingLogo" />
  <h1>T-Testing Testing Platform & Dashboard</h1>

  <p>SETS T-Testing provides a visual
dashboard for Management and
Testing Engineers, a powerful Test
Management Engine and a proven
innovative methodology to ensure
the most efficient use of testing
resources.</p>
<p>IT testing can be time consuming and expensive.
T-Testing provides both a methodology and a tool
to improve this process, making use of the client’s
existing development and test platforms.</p>
<p>
Interfaces are set up to send standard CSV format
files from the build and test servers to a journal
database, which stores all of the relevant results.
These may be recalled at any time.</p>
<p>
A common annoyance during testing is the case
of testing a system with known errors, but which is
actually being tested for a different aspect. The known
errors can overwhelm the information from the real
area of interest. The T-Testing tool and methodology
introduces a third result – “failed as expected” – to
isolate these expected errors.</p>
<p>
A unique dashboard presents the testing results in
various formats, with views suitable for management,
and views suitable for technical experts.</p>
<p>
SETS consultants will assist in setting up the system
and definition of Test Kits. If required, we will provide
training to the client’s own experts, to enable them to
take over most of the testing and reporting functions,
and thus ensuring a complete in-house testing
solution.<p>
<button type="button" onClick="window.open('files/SETSTTesting MWC Brochure V01.pdf')" id="ViewPDF">View PDF</button>

  <h2>Functional Scope</h2>
  <h3>1. Visual Dashboard</h3>
 
  <ul>
    <li>Overview of testing progress.</li>
    <li>Comparison with previous tests.</li>
    <li>Drill down to detailed results.</li>
    <li>Results may be “passed” / “failed” /
“failed as expected”.</li>
    <li>Overviews for management.</li>
    <li>Detailed views for technical experts.</li>
    
  </ul>
  
 
<h3>2. Integrated Testing System</h3>
  <ul>
    <li>User’s existing Repository, Build and
Test servers.</li>
    <li>Specification of Test Kits.</li>
    <li>Interface from Build Server to
Journal DB.</li>
    <li>Interface from Test Server to
Journal DB.</li>
    <li>CSV format files convey information
from the Build and Test Servers to the
Journal DB.</li>
    <li>The Journal DB stores results of the
builds and tests.</li>
    <li>The Dashboard interfaces to the
Journal DB and displays results.</li>
    </ul>
 
 
  <img src="images/ttesting_1.png" width="600" height="403" alt="ttesting_1" />
  
 
  <h3>3. Methodology</h3>
  <ul>
    <li>Preparation of Test Kits.</li>
    <li>Method of communicating from Build
and Test Servers to Journal DB.</li>
    <li>Extra flexibility with additional result –
“failed as expected” – to isolate
unexpected fails from expected fails.</li>
    <li>Testing results stored and always
available.</li>
    <li>Clear presentation of results.</li>
   
    </ul>
	
    <h3>4. Benefits</h3>
  <ul>
    <li>More efficient use of testing resources.</li>
    <li>Long term cost savings.</li>
    <li>Customisation to client hardware/
software configuration.</li>
    <li>Visual presentation of results suitable
both for management and technical
experts.</li>
    
   
    </ul>
  
  
  
  
  
  
  
  
  
  <img src="images/ttesting_2.png" width="600" height="565" alt="ttesting_2" /></div> <!-- content -->
  
</div> <!-- col624 -->
    
<div id="LastCol">
<?php require_once('ietvert/rightColGeneral.php'); ?>
</div> <!-- LastCol -->
    
</div> <!-- col810 -->
  
<?php require_once('ietvert/pageFooter.php'); ?>

</div> <!-- container -->

</body>
</html>
