#activitypubdev

Finally set up the plumbing for adding code coverage to the #FedBOX integration test containers. 💪 #ActivityPub #activitypubdev #fedidev

When I started the work on ActivityPub projects I fully embraced Maslow's Hammer adage. I wanted as much as possible in my services to go through the #ActivityPub vocabulary and I fully embraced the client to server API. But there are elements of a web application that require custom functionality no matter what, say changing a password. So for those I just added the capability of running commands through ssh. #ActivityPubDev #fedidev

I'm surprised at how many issues my new integration tests are finding. I already had an integration testsuite, but the way the #fedbox application was run was not in full isolation, and I expect some of the setup steps I had included don't really exist on a fresh install. We now build a fresh container image, start it up, provision it with mock data, and then run tests, but only through mechanisms that are available to a prospective server operator: CLI commands executed through SSH, and ActivityPub client to server operations. #fedidev #activityPubDev #activitypub

I've started working on generating RFC9421 compatible HTTP-Signatures in #GoActivityPub about a week and a half ago, but it felt more like a month. Writing tests for the client module took the bulk of this time and it was a proper slog. We did manage to increase code coverage from under 20% to 80% plus. This makes it a bit harder to migrate to a new API when the future version 1 of the library will be tagged, but the changes I have planned shouldn't be insurmountable. Now I just need to implement the verification, and I'll be done with what is a very large milestone for the library. #ActivityPubDev #fedidev #httpsig