From eca5989384c4aeb797664593b90aeccb36a87374 Mon Sep 17 00:00:00 2001 From: Aravinth Manivannan Date: Mon, 2 Oct 2023 13:15:07 +0530 Subject: [PATCH] feat: define result repository --- content/ftest/terminology.md | 12 +++++++++--- 1 file changed, 9 insertions(+), 3 deletions(-) diff --git a/content/ftest/terminology.md b/content/ftest/terminology.md index 065e806..8b137cc 100644 --- a/content/ftest/terminology.md +++ b/content/ftest/terminology.md @@ -6,8 +6,8 @@ weight = 2 ## Specimen -A specimen is an ActityPub or a ForgeFed instance that has to be tested -on ftest. +The target of a ftest test job. These are the ActityPub or ForgeFlux +implementations that must be tested for compliance. ## Job Manifest @@ -45,8 +45,14 @@ Each specimen has it's own directory in the control repository: └── Dockerfile ``` -### specimen docker-compose.yml +### Specimen docker-compose.yml The control repository _MUST_ contain a `docker-compose.yml` to spin up the specimen. It may include configuration files in the same directory, which to docker-compose file can rely on using bind mounts within the container. + + +## Result Repository + +Result repository contains the results of all the targets' jobs in JSON +format.