Slowly building up the test coverage... It's a long way to go, but at least it's improving. (And bugs are being fixed along the way. Guess that's showing the value of testing to begin with.)

#hubzilla-dev #testing #software_development

When I finally figure out what was wrong, I always feel really stupid. It appears, as often is the case, the solution was really simple once I knew what the problem actually was.

Fighting a CI pipeline that didn't provide any useful feedback, and that I wasn't able to replicate locally made the whole experience rather frustrating.

But in the end — after probing it repeatedly with slightly different configurations, and sneaky ways to try to get any useful logs out of it — the problem was of course on my end.

Don't include the id column when preloading test data into the database.

Can't remember why I included the id column in the first place, but it caused me much pondering. Even stranger was that it worked perfectly fine in my local dev/test setup.

At least the CI setup has become a lot more robust, and I've added a lot more logging to the test runs, so it should hopefully be easier to track down next time something mysteriously doesn't work.

#mywork #developerlife #ci #testing #hubzilla-dev

Wohoo! I have the Hubzilla test suite with a mysql database running in the framagit gitlab ci environment!

Was a pain to debug, as the local command line ci runner is useless and unsupported.

Now, try to get the tests running with postgres too, then!

And get the coverage report working... One step at the time...

#mywork #hubzilla #hubzilla-dev #ci

Hubzilla interop testing in Sandcastles?

I spent some time to get all the moving parts working here, but at least I'm able to get Hubzilla up and running and properly set up in the Sandcastles environment for fedi interop testing. Hopefully that will be useful to some.

https://github.com/Letterbook/Sandcastles/pull/2

There's still some minor issues though.- I'd like for it to be set up automatically without having to go through the setup wizard on first boot. That seemingly works by just supplying a configuration file, but then the database isn't set up, so nothing works.
- I also have to give the php-fpm container direct access to the fediverse network shared by all the different fedi instances in the sandbox, since the setup wizard checks for properly setup redirects and TLS certs during installation. Ideally I'd like the internal containers of the Hubzilla setup to just be on it's internal network. This may be a problem following from the first point, though.

Also I have not actually been able to test that if interoperates with Mastodon (the other software so far supported by the sandbox), since I don't know how to get the confirmation URL I need to finish the registration of a user there.

Still, I think this is a good starting point for being able to spin up multiple fediverse servers for interop testing. Now hoping I can land the PR in the upstream repo.

#mywork #fediverse #hubzilla #hubzilla-dev