From a66c595b1417195f185836fa444312fe73c99278 Mon Sep 17 00:00:00 2001
From: gdisirio <gdisirio@35acf78f-673a-0410-8e92-d51de3d6d3f4>
Date: Mon, 24 Nov 2014 08:49:36 +0000
Subject: git-svn-id: svn://svn.code.sf.net/p/chibios/svn/trunk@7530
 35acf78f-673a-0410-8e92-d51de3d6d3f4

---
 test/rt/test.dox | 28 ----------------------------
 1 file changed, 28 deletions(-)

(limited to 'test')

diff --git a/test/rt/test.dox b/test/rt/test.dox
index 87c68320b..2ff584055 100644
--- a/test/rt/test.dox
+++ b/test/rt/test.dox
@@ -27,34 +27,6 @@
  * order to verify the proper working of the kernel, the port and the demo
  * itself.
  *
- * <h2>Strategy by Component</h2>
- * The OS components are tested in various modes depending on their importance:
- * - <b>Kernel</b>. The kernel code is subject to rigorous testing. The test
- *   suite aims to test <b>all</b> the kernel code and reach a code coverage
- *   as close to 100% as possible. In addition to the code coverage, the kernel
- *   code is tested for <b>functionality</b> and benchmarked for <b>speed</b>
- *   and <b>size</b> before each stable release. In addition to the code
- *   coverage and functional testing a <b>batch compilation test</b> is
- *   performed before each release, the kernel is compiled by alternatively
- *   enabling and disabling all the various configuration options, the
- *   kernel code is expected to compile without errors nor warnings and
- *   execute the test suite without failures (a specific simulator is used
- *   for this execution test, it is done automatically by a script because
- *   the entire sequence can take hours).<br>
- *   All the tests results are included as reports in the OS distribution
- *   under <tt>./docs/reports</tt>.
- * - <b>Ports</b>. The port code is tested by executing the kernel test
- *   suite on the target hardware. A port is validated only if it passes all
- *   the tests. Speed and size benchmarks for all the supported architectures
- *   are performed, both size and speed regressions are <b>monitored</b>.
- * - <b>HAL</b>. The HAL high level code and device drivers implementations
- *   are tested through specific test applications under <tt>./testhal</tt>.
- * - <b>Various</b>. The miscellaneous code is tested by use in the various
- *   demos.
- * - <b>External Code</b>. Not tested, external libraries or components are
- *   used as-is or with minor patching where required, problems are usually
- *   reported upstream.
- * .
  * <h2>Kernel Test Suite</h2>
  * The kernel test suite is divided in modules or test sequences. Each Test
  * Module performs a series of tests on a specified kernel subsystem or
-- 
cgit v1.2.3