Analyze-the-results.md

-Once the testsuite finish, you can access to the results through your internet navigator.
+Once the testsuite finishes, you can access the results through your internet navigator.
 To proceed, open the `index.html` file that has been generated in the testsuite directory.
 
-# Main page
+## Main page
 
-![Capture_d_écran_de_2019-07-23_17-32-57](uploads/822def3eb3d85f50c995268cf58d13ea/Capture_d_écran_de_2019-07-23_17-32-57.png)
-_Main page of the testsuite showing various failed compilations and tests_
+You'll be redirected to the testsuite main page, showing the build, test, and code coverage sections, with summarized information about the whole test. For each item, a red cross ![ko](uploads/397a6076cb9ba95116a9a578f5a67397/ko.png) means a failure, while a green V ![ok](uploads/e44db76c513f51763fba543f02105c9e/ok.png) means a success. On the top left, the valid flag gives the general result. The code coverage is not taken into account to determine if the whole testsuite is valid or not.
 
-You will find a table containing the different tests that have been executed, and if their compilation and the test executions have succeeded or failed. You can click on each item to get more information.
+![Capture_d_écran_de_2020-03-30_17-11-44](uploads/a673974bc28e67774b73144290b73ea7/Capture_d_écran_de_2020-03-30_17-11-44.png)
+*Main page of the testsuite showing the build, test, and code coverage sections*
 
-# Compilation
+## Builds
 
-## Failed compilation
+If you click on the build item, you will access the build page. For each build, you'll see its name, the compiler, the version, some tags specific to this build, the modules loaded to compile, the configuration file, the job script content, and the output and error files generated by the job execution, as well as the execution time. If a build has failed (red cross), don't hesitate to analyze the content of the various files to understand what is the cause of the failure.
 
-A failed compilation is shown through a red cross. It indicates that one or several compilations have failed.
-You can access the compilation page by clicking on the red cross.
+![Capture_d_écran_de_2020-03-30_17-21-46](uploads/e9701a604ed6c1567cc75d6c9998a487/Capture_d_écran_de_2020-03-30_17-21-46.png)
+*Build page showing various compilations*
 
-![Capture_d_écran_de_2019-07-23_17-34-29](uploads/f3418248d6835c1571e9c10bdc640d39/Capture_d_écran_de_2019-07-23_17-34-29.png)
-_Compilation page_
+## Tests
 
-Print the output by clicking on the corresponding red cross:
+If you click on the test item, you will access the test page. For each test, you'll see an item with its name, its authors, a brief description, the alya modules it requires, the post process tool (`alya2pos`, `mpio2txt` or `none`), if the job has been relaunched one or several times because of a possible system failure (retry), and the global status of this job (showing the worst error that happened during this test execution with each of the build and mpi/openmp combination).
 
-![Capture_d_écran_de_2019-07-23_17-37-53](uploads/a2dcc7d2ce4db349c74de2ebf89f84af/Capture_d_écran_de_2019-07-23_17-37-53.png)
-_Output of the failed compilation_
 
-# Tests
-
-## Failed tests
 
 As for the compilation, you can get more insight into the test results by clicking on the corresponding red cross.