Drop support for TEST_REPORTS
We always use the text report on the UART so drop the other report
formats (Junit) and destinations (file over semihosting). This
simplifies the report generation code.
Change-Id: I64e105d8c773e31d63a4ed06999d24f946a40014
Signed-off-by: Sandrine Bailleux <sandrine.bailleux@arm.com>
diff --git a/docs/design.rst b/docs/design.rst
index 7163aad..d063790 100644
--- a/docs/design.rst
+++ b/docs/design.rst
@@ -21,17 +21,7 @@
Then the test session begins. The TF-A tests are executed one after the
other. Tests results are saved in non-volatile memory as we go along.
-Once all tests have completed, a report is generated. The TF-A tests currently
-supports 2 report formats:
-
-- Raw output, i.e. text messages over serial console.
-
-- Junit output, i.e. XML file generated over semihosting. This is useful when a
- post-processing tool needs to parse the test report, as it is more
- machine-friendly than the raw output.
-
-The report format to use is chosen at build time. For more information,
-refer to the section `Summary of build options`_ in the User Guide.
+Once all tests have completed, a report is printed over the serial console.
Global Code Structure
---------------------