|
The Fediverse is built on open standard protocols. Testing that implementations conform to those standards is important for interoperability. That's what we are working on with the FediTest project. Here's a first draft report of Webfinger server conformance for almost 100 Fediverse applications. A total of 1615 tests were run. Overview: https://feditest.org/contrib/results/2024-06-16/ -- more details by clicking through. (cont'd...) 3 comments
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...) 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) |
Gregory's Server
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...)