Programming

17278 readers

438 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 !webdev@programming.dev

founded 1 year ago

MODERATORS

snowe@programming.dev

Ategon@programming.dev

MaungaHikoi@lemmy.nz

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

submitted 2 months ago* (last edited 2 months ago) by akash_rawal@lemmy.world to c/programming@programming.dev

8 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] breadsmasher@lemmy.world 7 points 2 months ago (6 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.

[–] akash_rawal@lemmy.world 4 points 2 months ago (5 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.

[–] Miaou@jlai.lu 1 points 2 months ago

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

load more comments (4 replies)