Quick teaser for the weekend:
-
Quick teaser for the weekend:
1. run feditest with a few arguments
2. spins up two instances of Mastodon, with redis and sidekiq etc etc
3. at locally provisioned hostnames, with TLS certs locally generated with a local CA
4. Test has Mastodon instance1, on behalf of user1 at instance1, send "Good morning" to user2 at instance2.
5. Waits until the message has arrived with user2 at instance2(cont'd)
-
Fediverse Test Suitereplied to Fediverse Test Suite last edited by
(cont'd)
6. Checks message integrity and reports ("degraded" -- there's extra HTML not in the original message)
7. Takes down both Mastodon instances and all daemons etc.Elapsed time: 1 min, 22 sec on my MacBook Pro.
And 10 sec of those are merely waiting from the time the Mastodon instances are supposed to be functional but sometimes aren't.
(Not released yet)
-
GunChleocreplied to Fediverse Test Suite last edited by
-
Renaud Chaputreplied to Fediverse Test Suite last edited by
@feditest I am curious about those 10s, can you explain more? Do you use the built in healthcheck endpoikt to determine when the webserver is available?
-
Fediverse Test Suitereplied to Renaud Chaput last edited by
@renchap Just a very simple hack -- trivial to implement and works for all software. Doing a health check query is more complicated and is software-specific so we kept it simple for now.
Feel free to file an issue