Working on FediTest, we learned quickly that a simple...

Fediverse Test Suite's posts Post Back to profile

Working on FediTest, we learned quickly that a simple pass/fail is not a very good report for many tests of Fediverse protocols. So our reporting is more complex.

We distinguish not only between PASS and FAIL but PASS and a variety of non-PASS conditions.

(cont'd...)

Like 19 June at 19:39 | Open on mastodon.social

2 comments

Fediverse Test Suite

For example: there are implementations that do not conform to what the standard says is a MUST, but it's unlikely that will cause any interoperability issues.

Often they have good reasons for doing what they do, such as reporting "504 Gateway Timeout" -- a case the WebFinger standard does not consider.

How do we report that? So that's why you see the 4x4 matrix at the top of the report and the different shades of red.

(cont'd...)

19 June at 19:40 | Open on mastodon.social

Fediverse Test Suite

Note: our categorization is experimental and you may disagree with it. We would love to hear suggestions on how to do better.

Of course, this is new code, and our tests may have bugs, too. To discuss, join us on Matrix and/or file issues.

More info and how to test your own implementation: Go to https://feditest.org/

(end)

19 June at 19:41 | Open on mastodon.social