Rework QA main page

To make it easier for newcomers to understand the QA in Apertis rework
the main page to provide an introduction and rationale.

Signed-off-by: Walter Lozano <walter.lozano@collabora.com>

content/qa/_index.md

@@ -9,7 +9,21 @@ aliases = [
 ]
 +++
 
-This is the page for the Quality Assurance team. It includes links for
+One of the key strengths of Apertis is the testing done to the images allowing
+to catch regressions early in the development cycle. The QA process heavily relies
+in [LAVA](https://lava.collabora.dev/) to perform automated tests on the
+reference hardware, which is then reported on [QA website](http://qa.apertis.org/).
+
+Running tests on real hardware allows developers and product owners to make sure
+that products meet their expectations on the target platform. Thanks to these
+integration tests the combination of hardware, kernel base system and application
+is stressed in different ways to ensure the quality of the final product.
+
+Apertis currently runs:
+- Automated tests on daily basis for daily builds
+- Automated and manual tests on released images
+
+This section is for the Quality Assurance team. It includes links for
 QA services, documentation, tests and any information related to
 the different QA processes in the project.
 
@@ -19,13 +33,6 @@ Apertis uses the [Apertis issues board](https://gitlab.apertis.org/infrastructur
 
 Community members are encouraged to contribute to it by reporting any issues they may find while working with Apertis, or by suggesting improvements to the project.
 
-# Weekly tests reports
-
-The images are tested weekly using both manual and automated tests as
-documented on the [test case site](https://qa.apertis.org/).
-Reports of the testing performed are available on the
-[test report site](https://qa.apertis.org/).
-
 # Services
 
 - [LAVA (Linaro Automated Validation Architecture)](https://lava.collabora.dev/)