ftest tests for the Nodeinfo protocol

Find a file

Aravinth Manivannan b483a9b971 feat: add schema validation		2023-10-01 14:14:32 +05:30
.reuse	feat: init	2023-10-01 13:36:43 +05:30
LICENSES	feat: init	2023-10-01 13:36:43 +05:30
.dockerignore	feat: init Docker pkg	2023-10-01 13:55:54 +05:30
.env_sample	fix: rm FTEST_USER. It is irrelevant for this test	2023-10-01 13:56:24 +05:30
.gitignore	feat: init	2023-10-01 13:36:43 +05:30
.woodpecker.yml	feat: init Docker pkg	2023-10-01 13:55:54 +05:30
Dockerfile	feat: init Docker pkg	2023-10-01 13:55:54 +05:30
README.md	fix: rm FTEST_USER. It is irrelevant for this test	2023-10-01 13:56:24 +05:30
requirements.txt	feat: bootstrap w forgeflux/webfinger-test boiler plate & test links attr	2023-10-01 13:39:27 +05:30
run.py	feat: add schema validation	2023-10-01 14:14:32 +05:30

README.md

Nodeinfo tests for ForgeFlux/ftest

TODO

Write code to upload to ftest server
Package Docker container
Upload to Docker Hub

Environment Variables

Please see .env_sample

NAME	Purpose	Example
`FTEST_AUTH`	Authorization token for uploading test results to ftest server	a random-generated string that will be provided by ftest server
`FTEST_HOST`	The URL of the ftest's instance to which tests results should be uploaded	`http://localhost:5000`, if an ftest implementation is running on localhost at port 5000
`FTEST_TARGET_HOST`	The URL of the implementation's instance against which tests will be run	`http://localhost:3000`, if Forgejo or any other Nodeinfo implementation is running on localhost at port 3000

Usage

cp .env_sample .env # edit and populate .env with the right values
source .env
python run.py

Docker

cp .env_sample .env # edit and populate .env with the right values
source .env
docker run \
 -e FTEST_AUTH=$FTEST_AUTH \
 -e FTEST_TARGET_HOST=$FTEST_TARGET_HOST \
 -e FTEST_HOST=$FTEST_HOST forgeflux/nodeinfo-test

Demo

Successful run:

TODO

Please open to see logs

Failed run:

TODO

Please open to see logs