-
Notifications
You must be signed in to change notification settings - Fork 1
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Add blog post for today
- Loading branch information
Johannes Ernst
committed
Jan 30, 2024
1 parent
2a1a5f3
commit 1a708c8
Showing
9 changed files
with
291 additions
and
4 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,54 @@ | ||
--- | ||
title: About FediTest | ||
--- | ||
|
||
<style> | ||
table.people { | ||
width: 100%; | ||
} | ||
table.people td:nth-child(1) { | ||
width: 30%; | ||
} | ||
table.people td:nth-child(2) { | ||
width: 30%; | ||
text-align: center; | ||
} | ||
table.support td:nth-child(1) { | ||
width: 30%; | ||
background: #404040; | ||
} | ||
table.support img { | ||
max-width: 100%; | ||
} | ||
</style> | ||
|
||
FediTest is a collaborative open-source project to test interoperability in the | ||
Fediverse. | ||
|
||
<div style="height: 3em"></div> | ||
|
||
Repos: | ||
|
||
* [github.com/fediverse-devnet/feditest.org](https://github.com/fediverse-devnet/feditest.org/): this site | ||
* More to come | ||
|
||
<div style="height: 3em"></div> | ||
|
||
We gratefully acknowledge support from the following organizations: | ||
|
||
<table class="support"> | ||
<tr> | ||
<td> | ||
<a href="https://nlnet.nl/core"><img src="/assets/NGI0Core_tag.svg"></a> | ||
<a href="https://nlnet.nl/"><img src="/assets/nlnet-banner.png"></a> | ||
</td> | ||
<td> | ||
This project was funded through the <a href="https://nlnet.nl/core">NGI0 Core</a> | ||
Fund, a fund established by <a href="https://nlnet.nl/">NLnet</a> | ||
with financial support from the European Commission's | ||
<a href="https://ngi.eu/">Next Generation Internet</a> programme, under the | ||
aegis of DG Communications Networks, Content and Technology under grant agreement | ||
N<sup>o</sup> 101092990. | ||
</td> | ||
</tr> | ||
</table> |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,40 @@ | ||
--- | ||
title: Slides shown at the W3C's Social Testing Task Force today | ||
date: 2024-01-30 | ||
author: Johannes Ernst | ||
authorurl: https://j12t.org/ | ||
--- | ||
|
||
The W3C's Social Community Group -- shepherd of the ActivityPub and ActivityStreams | ||
standards -- has a Testing Task Force. It had a meeting today, and I showed these slides, | ||
figured I put them here, too. (These are work in progress, and more notes than "presentation" | ||
slides, my apologies for the lack of prettiness.) | ||
|
||
First, on user stories. Like for all systems, it is useful to consider who we write | ||
a Fediverse test suite for, and what they are trying to accomplish with it. In this | ||
slide, we have two personas shown in separate columns, with a list of what they want to | ||
do and why. | ||
|
||
![User stories for FediTest](/assets/2024-01-30/user-stories-for-feditest.jpeg) | ||
|
||
Other personas might also want to run certain tests, as was pointed out during the call | ||
today. For example, an end user might want to determine why somebody else's Fediverse | ||
server does not accept their content. This is out of scope for FediTest, however. | ||
|
||
Secondly, on the question of: how do we translate the various standards documents | ||
(like ActivityPub, or WebFinger) into the set of tests that test them? And then, how | ||
do we make sure we have good test coverage, and how do we evolve tests with the specs | ||
change? | ||
|
||
I came up with something very hacky, which is to simply copy the spec HTML, and inline | ||
test annotations right there. Here is an example. The things in the red boxes are my | ||
test annotations into the ActivityPub standard. They are added by means of a custom | ||
web component (`<annost-test>` at the bottom) which renders into the box with the red | ||
border. | ||
|
||
![Test specifications inlined into the standard](/assets/2024-01-30/test-annotations-in-spec.jpeg) | ||
|
||
Is it a good idea? Not sure yet, and it certainly can be made better, but perhaps | ||
worth considering. It certainly wins today's prize for hackiness :-) | ||
|
||
(This is also worth a separate blog post in the future.) |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters