@[email protected] Thanks <3

Do you plan other tests for the ActivityPub part

Yes! I'm trying to ship #ftest now. I'll work on tests for #ActivityPub and #ForgeFed after that (next week, probably :))

Per the documentation, #GoToSocial doesn't have a Web UI to create new accounts. There's an API endpoint for that, but it seems to require an app token, which I'm guessing requires an admin account.

So the only way to create an admin account on GoToSocial, is using the CLI tool. #ftest uses Docker containers for spinning up specimen environments and running initialization workflows against them. To use the CLI tool, I'd have to let init workflows run arbitrary shell commands on the host machine --- not good.

So I've created a thin wrapper around the upstream Docker container image, which will let me use the admin CLI using the command docker-compose attribute.|

• Source
• Container img

Moved on to #ActivityPub testing. I've implemented a basic check for Object as defined in the spec.

This time, I'm using behave, a behavior-driven-development (BDD) library for testing. With BDD, we can have natural language descriptions for tests (like this one), which will enable a non-programmer person to understand what the tests are doing.

The ActivityPub suite share a lot of code with the WebFinger and Nodeinfo suites, so I'm also refactoring the shared code into a library that can be used to write #ftest suites in Python. It contains all the boilerplate/integration to work with #ftest, so that might be useful.

Source code: https://git.batsense.net/ForgeFlux/ap-test
Container image: https://hub.docker.com/r/forgeflux/ap-test/

I will run this suite against #Forgejo and report my findings below :))

@forgeflux