Programming

17437 readers

187 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Follow the programming.dev instance rules
Keep content related to programming in some way
If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities [email protected]

founded 1 year ago

MODERATORS

[email protected]

Self terminating container images for real world dependencies to support your unit tests (gitlab.com)

submitted 3 months ago* (last edited 3 months ago) by [email protected] to c/[email protected]

8 comments fedilink hide all child comments

top 8 comments

sorted by: hot top controversial new old

[–] [email protected] 8 points 3 months ago (1 children)

What is the specific use case of these, relating to unit testing?

Why not just have the container execute unit tests, once that process ends and the container closes itself? This wouldn’t need anything additional.

[–] [email protected] 4 points 3 months ago (2 children)

I don't get it, how would a database container run your unit tests? And unless you know some secret option to stop the database after, say, it is idle for a few seconds, it will continue running.

The purpose is to test database dependent code by spinning up a real database and run your code against that.

[–] [email protected] 14 points 3 months ago* (last edited 3 months ago) (2 children)

Ah! That’s what I didn’t understand. So its not a container for executing unit tests. Its a container for dependencies to support unit tests. That is not clear from the readme unless I missed something

edit - the title could be “Self terminating containers for real world dependencies to support your unit tests”

[–] [email protected] 11 points 3 months ago (1 children)

This feels more like an integration test than a unit test to me. Maybe that's not an important distinction to make, but it feels like it would also help communicate intent.

[–] [email protected] 12 points 3 months ago

I'm reading this scratching my head going "If your unit tests need a database they ain't a unit test".

[–] [email protected] 2 points 3 months ago

Thanks man, my brain was short-circuited on Testcontainers so I couldn't write better. Also I am stealing the title.

[–] [email protected] 1 points 3 months ago

So it's not for unit tests, that's where the confusion stems

[–] [email protected] 3 points 3 months ago

cool, we need more tooling around rootless docker / podman