From 974fcedc0b9a42b8476eba310f59c76fbc727bb4 Mon Sep 17 00:00:00 2001
From: Pedro Santos Neves <10762799+Neves-P@users.noreply.github.com>
Date: Mon, 14 Oct 2024 15:22:52 +0200
Subject: [PATCH 1/2] Update bot docs

Update examples to use `software.eessi.io` and include abridged information on the test step.
---
 docs/bot.md | 14 +++++---------
 1 file changed, 5 insertions(+), 9 deletions(-)

diff --git a/docs/bot.md b/docs/bot.md
index 64707a4b45..25eadac16c 100644
--- a/docs/bot.md
+++ b/docs/bot.md
@@ -97,7 +97,7 @@ Separate filters with a space, order of filters does not matter.
 For example:
 
 ```
-bot: build repo:eessi-hpc.org-2023.06-software arch:x86_64/amd/zen2
+bot: build repo:eessi.io-2023.06-software arch:x86_64/amd/zen2
 ```
 
 #### Multiple build instructions
@@ -108,8 +108,8 @@ repositories, and CPU targets. Specify one build instruction per line.
 For example:
 
 ```
-bot: build repo:eessi-hpc.org-2023.06-software arch:x86_64/amd/zen3 inst:aws
-bot: build repo:eessi-hpc.org-2023.06-software arch:aarch64/generic inst:azure
+bot: build repo:eessi.io-2023.06-software arch:x86_64/amd/zen3 inst:aws
+bot: build repo:eessi.io-2023.06-software arch:x86_64/amd/zen4 inst:azure
 ```
 
 !!! note
@@ -154,15 +154,11 @@ which was created by the `bot/check-result.sh` script.
 
 ## Testing { #testing }
 
-!!! warning
-    The test phase is not implemented yet in the bot.
-
-    We intend to use the [EESSI test suite](https://github.com/EESSI/test-suite)
-    in different OS configurations to verify that the software that was built works as expected.
+The bot also runs tests in the [EESSI test suite](test-suite/index.md) if these match the software being installed. These tests are run after the build step by the bot through the `bot/test.sh` script. The mapping of which tests will run given the built software is defined in `tests/eessi_test_mapping/software_to_tests.yml`. Lastly, the job manager reports a summary of the test results created by the `bot/check-test.sh` script.
 
 ## Deploying { #deploying }
 
-To deploy the artefacts that were obtained in the build phase, you should add the `bot: deploy` label
+To deploy the artefacts that were obtained in the build phase, you should add the `bot:deploy` label
 to the pull request.
 
 This will trigger the event handler to upload the artefacts for ingestion into the EESSI repository.

From 9e1a323f5b1c928f43a6c90abd4fcd1c76298bb1 Mon Sep 17 00:00:00 2001
From: Pedro Santos Neves <10762799+Neves-P@users.noreply.github.com>
Date: Mon, 14 Oct 2024 15:26:22 +0200
Subject: [PATCH 2/2] prettify link

---
 docs/test-suite/index.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/test-suite/index.md b/docs/test-suite/index.md
index 8aae42803e..e22b340052 100644
--- a/docs/test-suite/index.md
+++ b/docs/test-suite/index.md
@@ -9,7 +9,7 @@ To get started, you should look into the [installation and configuration guideli
 
 To write the ReFrame configuration file for your system, check [ReFrame configuration file](ReFrame-configuration-file.md).
 
-For which software tests are available, see [available-tests.md](available-tests.md).
+For which software tests are available, see [available tests](available-tests.md).
 
 For more information on using the EESSI test suite, see [here](usage.md).