The target of a ftest test job. These are the ActityPub or ForgeFlux implementations that must be tested for compliance.
Contains information on the test environment, initialization code and the test suites that has to be run on the specimen
- Flagship instance: git.batsense.net/ForgeFlux/ftest-control
Each specimen has it's own directory in the control repository:
23:50 atm@lab ftest-control ±|gotosocial ✗|→ tree └── targets ├── forgejo │ ├── conf │ │ └── app.ini │ ├── docker-compose.yml │ └── ftest.toml └── gotosocial ├── data │ └── config │ └── config.yaml ├── docker-compose.yaml └── Dockerfile
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 contains the results of all the targets' jobs in JSON format.