Skip to content

WIP: Tests for streams

csaurus requested to merge csaurus/pleroma:test/streams into develop

I started work on this, though looking at the test I wrote modeled after the other ones, they seem kind of tautological? The existing tests don't seem to touch any of the logic which initializes connections and names topics (in the case of user or direct). Since this is where !129 (merged) failed I'd like to put some coverage in there.

I'm tempted (and have started work) on making a version that goes through the whole process of logging in, posting via the Masto API, and having another logged in user which waits for the message. Are there thoughts on whether this is overkill, a good direction to head in, or should be broken out into a separate place like a "mastodon_socket_test.exs"?

Merge request reports