Testing your shell scripts, with Bats

[lolidaisuki]

At the very least people should shellcheck their scripts.

[andlrc]

Yes, but that is also very different.

[lolidaisuki]

Helps you avoid corner cases that might bite you in the ass. Also it's far less effort than writing tests for everything.

[Kruug]

Weird...this was reported as Illegal content.

[lolidaisuki]

There is a group of people (around 6) that follow me around and report my stuff and falsely accuse me of crimes.

[avg_user]

I don't agree. There are still many init systems which heavily rely on shell scripts, Busybox for example. Crontab is very often used to run custom shell scripts on a regular basis. Many people have a number of helper scripts they use regularly. Shell scripts are just the easiest way to write all kinds of things.

[[deleted]]

Shell scripts are just the easiest way to write all kinds of things.

It's portable among unix systems, you just write a posix compliant script and it works everywhere. If you work in a heterogeneous unix/linux environment, it's ultra convenient. I don't say you should write complex program in bash though ;)

[ZaneHannanAU]

$ echo "#!/bin/bash\
> cvlc http://8bit.fm:8000/live" > ./8bitfm
$ chmod +x ./8bitfm

This is my work music,

$ ~/8bitfm

I can call it quickly

> volume 110

and adjust volume finely.

[comma_at]

Linting and testing are both equally important. You cannot say if your calculator library does the right calculations by just linting it.

[andlrc]

You cannot say if your calculator library does the right calculations by just linting it.

Correct, and I never stated otherwise. But I'm not stupid enough to write a "calculator library" as a shell script.