| ... | ... | @@ -4,8 +4,28 @@ Goal: in the [Forgejo end-to-end test suite](https://code.forgejo.org/forgejo/en |
|
|
|
|
|
|
|
The Forgejo end-to-end test suite performs local (self-contained) deployments and runs tests for interactions between two (or potentially more) instances: Forgejo to Forgejo, or Forgejo to Forgejo Runner, or federation between Forgejo and another ActivityPub software such as Mastodon.
|
|
|
|
|
|
|
|
The task here is:
|
|
|
|
The initial task here has two parts:
|
|
|
|
|
|
|
|
- to add Mastodon to the available software instances that the test suite can deploy,
|
|
|
|
- to implement at least one federation test between Forgejo and Mastodon.
|
|
|
|
- add one ActivityPub-capable non-forge software to the available software instances that the test suite can deploy: Mastodon
|
|
|
|
- implement at least one federation test between Forgejo and Mastodon: [Federated User Activity Following](https://codeberg.org/forgejo/forgejo/pulls/4767) (currently WIP).
|
|
|
|
|
|
|
|
Possible follow-on tasks include:
|
|
|
|
|
|
|
|
- create API abstractions for common test actions (star, follow...) to share across different instance types
|
|
|
|
- bring in a test suite framework to better organise the test suite
|
|
|
|
- bring in a Fedi test framework (see for instance [Letterbook Sandcastles](https://github.com/Letterbook/Sandcastles))
|
|
|
|
- implement more federation tests (user following, star, ...)
|
|
|
|
- implement more federation-capable software instances (Vervis, GTS, ...)
|
|
|
|
|
|
|
|
|
|
|
|
## Add Mastodon Deployment
|
|
|
|
|
|
|
|
- Use the (official) Mastodon container image as a base
|
|
|
|
- create (minimal) Mastodon configuration-settings
|
|
|
|
- create Mastodon user account etc.
|
|
|
|
- create Mastodon test data (if needed)
|
|
|
|
- solve TLS/HTTPS/plain-text
|
|
|
|
|
|
|
|
## Add test for Federated User Activity Following
|
|
|
|
|
|
|
|
... |
|
|
\ No newline at end of file |
