https://feditest.org/Recent content on FediTestHugo -- gohugo.ioen-UShttps://feditest.org/blog/2025-02-02-feditest-at-fosdem/Mon, 03 Feb 2025 00:00:00 +0000https://feditest.org/blog/2025-02-02-feditest-at-fosdem/There were a of presentations, discussions and generically good vibes about the open social web and ActivityPub at FOSDEM, the open-source conference in Brussels, Belgium, this past weekend. I gave a FediTest presentation at the FOSDEM Social Web After Hours at Hackerspace Brussels. In spite of it being rather late, there were lots of good questions and quite some interest in testing and FediTest in particular. Somebody learned about FediTest in this talk, ran FediTest against their own implementation and reported that they fixed several bugs within 24 hours of the presentation.https://feditest.org/blog/2024-11-21-feditest-presentation-at-w3c-swicg/Tue, 19 Nov 2024 00:00:00 +0000https://feditest.org/blog/2024-11-21-feditest-presentation-at-w3c-swicg/I will give an update about the FediTest project to the World Wide Web Consortium’s Social Web Community Group’s Testing Task Force: Thursday, November 21, 2024, 10am pacific time Online, using Jitsi: https://meet.jit.si/socialcg-testing Draft subjects to cover: The various problems that need(ed) solving to make FediTest work Updated FediTest architecture and approach Protocol vs system tests Demo Remaining challenges and planned approach Putting FediTest to work with more applications and more test coverage Come by if you are interested.https://feditest.org/blog/2024-11-09-feditest-presentation-at-seagl/Sat, 09 Nov 2024 00:00:00 +0000https://feditest.org/blog/2024-11-09-feditest-presentation-at-seagl/Every year, seagl.org, the Seattle GNU/Linux Conference, takes place in Seattle. I had the opportunity to present our work with FediTest in an hour-long session Saturday morning. This was a more general technical audience, not particularly focused on the social web and the Fediverse: almost everybody had heard of the Fediverse, but very few hands went up when I asked who could explain how it works, technically. So I spent a bit more time talking about what the various involved protocols do and how they interact, and only from there launched into the FediTest discussion.https://feditest.org/blog/2024-10-24-feditest-journey-surprises/Thu, 24 Oct 2024 00:00:00 +0000https://feditest.org/blog/2024-10-24-feditest-journey-surprises/We released FediTest V0.4 yesterday, which is a significant step forward towards making FediTest more useful when testing Fediverse implementations in the real world. The journey has been longer and more time-consuming than we(*) expected. I thought I outline a few reasons why. We first thought we could build FediTest on top of the PyUnit unit testing framework. It does a lot of things already that we wanted FediTest to do, like discovering tests and producing reports etc.https://feditest.org/blog/2024-09-13-feditest-session-at-fediforum/Fri, 13 Sep 2024 00:00:00 +0000https://feditest.org/blog/2024-09-13-feditest-session-at-fediforum/FediForum is an unconference “for the people who move the Fediverse forward”. It took place for the fourth time September 12-14, 2024, online. (Disclaimer: I’m an organizer.) Naturally, I ran a session on FediTest there. Steve Bate was there as well. We had a number of Fediverse developers there, including Ryan Barrett and Jesse Karmani. (There were others but following FediForum conventions, I don’t want to publish their names as they didn’t add their names to the public attendee list of the session.https://feditest.org/blog/2024-08-08-feditest-at-dwebcamp/Thu, 08 Aug 2024 00:00:00 +0000https://feditest.org/blog/2024-08-08-feditest-at-dwebcamp/Organized again by the Internet Archive, DWebCamp this year brought together over 500 technologists, rights advocates, activists, artists, entrepreneurs, social and otherwise, and many more, for 3+ days of conference and unconference under the California Redwoods. Redwoods, tents and laptops in the same setting? Slide presentations and marshmallows? Apparently it works! I had the opportunity to run a workshop on FediTest, and the larger question of how can we ever ensure the quality of large-scale decentralized, heterogeneous systems that we are now building, such as in the Fediverse.https://feditest.org/blog/2024-06-13-some-tentative-decisions/Thu, 13 Jun 2024 00:00:00 +0000https://feditest.org/blog/2024-06-13-some-tentative-decisions/As FediTest progresses, some questions are emerging, and the right answers aren’t entirely obvious. In this post, I list some of the questions and attempt to answer them. This is a draft, and everything is very tentative: we are looking for feedback and are happy to decide otherwise if somebody’s reasoning is better than our own. Will the FediTest project regularly run tests and publish the results? We have no current plans to do so.https://feditest.org/blog/2024-06-05-early-results-webfinger/Wed, 05 Jun 2024 00:00:00 +0000https://feditest.org/blog/2024-06-05-early-results-webfinger/For today’s meetup, here are some materials. As a reminder: FediTest user stories FediTest architecture We can report on the first back of testing for the simplest part of this all: WebFinger service conformance. Annost-annotated RFC 7033 (WebFinger): this is where we identified what to test. Test results as test matrix: provides an overview over 17 tests against 39 implementations. Test results as test transcript: more detail, one implementation at a time.https://feditest.org/blog/2024-04-30-update/Tue, 30 Apr 2024 00:00:00 +0000https://feditest.org/blog/2024-04-30-update/We are making progress! Here is where we are: The FediTest framework now has the right structure. (I think …) Here are the core abstractions: TestPlan, consisting of one or more TestPlanSessions, each of which is a sequence of tests that are run against a Constellation of Nodes. TestPlans can be generated automatically and edited manually for maximum flexibility. A Constellation of Nodes is essentially a simulated, small Fediverse consisting of two or more Nodes running software and attempting to communicate with each other.https://feditest.org/blog/2024-04-18-iiw-feditest-architecture/Thu, 18 Apr 2024 00:00:00 +0000https://feditest.org/blog/2024-04-18-iiw-feditest-architecture/We covered FediTest (with demo!) in a session at Internet Identity Workshop IIW38 at the Computer History Museum in Mountain View, CA, today. I made a new slide with the FediTest architecture which I think is better than what I had before. I think it communicates more clearly how it works.https://feditest.org/blog/2024-04-09-earliest-access/Tue, 09 Apr 2024 00:00:00 +0000https://feditest.org/blog/2024-04-09-earliest-access/Warning Development has moved on since this blog post. Go to Quickstart for current information. If you are interested in running basically the same thing that was shown in the recent FediTest show and tell, here is how you do that. There are many disclaimers, as this is early work. It doesn’t really test much. The focus of this early(est) release is to let you play with the approach we are taking, so we can get feedback as early as possible and build something that might actually be useful :-)https://feditest.org/blog/2024-03-29-early-feedback/Fri, 29 Mar 2024 00:00:00 +0000https://feditest.org/blog/2024-03-29-early-feedback/We did a few rounds of early show-and-tell, including: this session in a meeting of the Fediverse Developer Network; this session at FediForum; and a few one-on-one sessions with potential users. The main points of feedback were: Ah, interesting, is it done yet? Comment: I take this as something positive :-) You are doing something complicated (supporting several nodes in a server constellation). Can’t you start by doing something simpler, such as simply running a few curl commands against a server in the cloud?https://feditest.org/blog/2024-02-28-early-show-and-tell-and-feedback/Wed, 28 Feb 2024 00:00:00 +0000https://feditest.org/blog/2024-02-28-early-show-and-tell-and-feedback/Update: the recording of the meeting and some notes are now online here on the FediDevs.org site. Some good questions and discussion. We seem to be going in roughly the right direction based on feedback, so we’ll charge on!! Release early and often, they say. For some complex projects with complex requirements, it’s also useful to show-and-tell early and often, and get direct, verbal feedback as soon as possible. FediTest is one of them.https://feditest.org/blog/2024-02-12-components/Mon, 12 Feb 2024 00:00:00 +0000https://feditest.org/blog/2024-02-12-components/To create the Fediverse Test Suite, we need a number of components: 1. The actual tests For example, we want to test that: An actor file has the right format. An actor can follow another actor on another server, and their “following” and “follower” collections are updated accordingly. The content of a “note” post does not get mangled when transmitted from one server to another server running different software. Each of those needs to have code that exercises the server(s) under test, and observes that the server(s) under test do the right thing.https://feditest.org/blog/2024-02-06-what-is-a-test-suite-for-the-fediverse/Mon, 05 Feb 2024 00:00:00 +0000https://feditest.org/blog/2024-02-06-what-is-a-test-suite-for-the-fediverse/Let’s start with the term Test Suite. This is what Wikipedia has to say about it: In software development, a test suite, … is a collection of test cases that are intended to be used to test a software program to show that it has some specified set of behaviors. About Test Case, it says: … a test case is a specification of the inputs, execution conditions, testing procedure, and expected results that define a single test to be executed to achieve a particular software testing objective, such as to exercise a particular program path or to verify compliance with a specific requirement.https://feditest.org/blog/2024-01-30-testing-tf-slides/Tue, 30 Jan 2024 00:00:00 +0000https://feditest.org/blog/2024-01-30-testing-tf-slides/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.https://feditest.org/blog/2024-01-29-hello-world/Mon, 29 Jan 2024 00:00:00 +0000https://feditest.org/blog/2024-01-29-hello-world/Need for a Fediverse Test suite? ✔ Check. Basics of a plan? Right here! ✔ Check. Funding? Secured! Thanks NLNet! ✔ Check. So, Hello World, let’s get this project started! We will be hosting periodic community meetings to demo what we are building, discuss project progress, and get community feedback. So far, we have not scheduled one because we are just starting and don’t have anything to show yet.https://feditest.org/blog/2023-08-11-swicg-presentation/Fri, 11 Aug 2023 00:00:00 +0000https://feditest.org/blog/2023-08-11-swicg-presentation/Note This early plan was presented to the W3C’s Social Web Community Group in August 2023 and is republished here. Corresponding slides: 1 2 3 4. The problem Core premise of the Fediverse is that users can use any Fediverse servier-side app they choose (say “App A” such as Mastodon) to interact with others on the Fediverse, even if they use a different server-side “App B”, and when they do so, the interaction “will work”.