Integration tests using outdated Mastodon versions

[bocops]

We currently have integration tests defined for the following Mastodon versions:

• v300 - even the latest 3.x branch is considered to be at end of life (release notes)
• v402 - same (release notes)
• v410 - same (release notes)

There's the additional problem of these test suites depending on an authentication method that was removed with Mastodon 4.3.1 (#503), so would need additional rewrite.

I think we need to

• remove the v300 and v402 tests suites
• discuss if we need integration testing at all
• depending on the outcome, either update v410 to v430, or remove that as well
• handle docker files accordingly

[PattaFeuFeu]

I’m entirely onboard with removing v300 and v402. I’ll do that part of the removal.

Whether we should keep integration tests or not is what I’m not yet sure about. They’re not even ran in intervals currently, nor on every PR. I don’t have a setup to run them currently, not sure about you. I’m slightly leaning towards removing them as a whole and rather only keep what we actually use regularly. 🤔

[bocops]

I don't have them set up at the moment, either. In the past, if I needed to test responses of an actual Mastodon server, what I typically did was to modify an existing sample for my need, or create a new one that then sometimes became part of the PR.

Running samples once is not the same as testing periodically, but I think it is sufficient for what we're doing here. So perhaps writing/updating matching samples could become a requirement of PRs that implement new functionality?

[PattaFeuFeu]

That matches my approach verbatim.

So perhaps writing/updating matching samples could become a requirement of PRs that implement new functionality?

Good idea 👍