mastouille.fr est l'un des nombreux serveurs Mastodon indépendants que vous pouvez utiliser pour participer au fédiverse.
Mastouille est une instance Mastodon durable, ouverte, et hébergée en France.

Administré par :

Statistiques du serveur :

594
comptes actifs

#testcontainers

0 message0 participant0 message aujourd’hui

This week’s post is the third and final in my series about running tests on #Kubernetes for each pull request. In the 1st post, I described the app and how to test locally using #Testcontainers and in a #GitHub workflow. The second post focused on setting up #GKE and running end-to-end tests on Kubernetes.

In this post, I’ll show how to benefit from the best of both worlds with #vCluster: a single cluster with testing from each PR in complete isolation from others.

blog.frankel.ch/pr-testing-kub

A Java geek · Pull request testing on Kubernetes: vCluster for isolation and costs control
Plus via Nicolas Fränkel 🇺🇦🇬🇪
Suite du fil

#Testcontainers are not ideal, as configuring them to run your tests efficiently is not as trivial as it's glossed; I explained that in
A simple way to configure the integration tests pipeline" (event-driven.io/en/configure_c). Still, undeniably, it can speed up the initial ramp-up phase and, if used wisely, can be a decent way to handle common testing dependencies.

2/2

event-driven.ioA simple way to configure integration tests pipeline - Event-Driven.ioEvent-Driven by Oskar Dudycz

#Testcontainers became a popular way of setting up dependencies for integration testing. They already provide the default configurations for tools like PostgreSQL, Kafka, MongoDB etc. Yet, sometimes you need to use something a bit less mainstream, for instance, Event Store as your event store. How to do it?

I explained that in my latest article, read more in: event-driven.io/en/custom_test

1/

event-driven.ioHow to configure a custom Test Container on the EventStoreDB example - Event-Driven.ioEvent-Driven by Oskar Dudycz

In the next iteration of my app i want to have proper test and CI for x86_64 and arm64.
So the next steps will be:
- try out #testcontainers to provide a #VaultWarden instance
- maybe send a PR with said container definition upstream
- get the CI running according to the #Relm4 documentation. That said i need to convert the actions used in the example to #ForgejoActions since i am hosting on #CodeBerg.

Then i will work on more features like the password dialog and the detail page.