jbrains, 3 months ago Trying to do something like #TDD with #jq I'm using Golden Master technique and I've committed the expected output to git. This is "assert all remains well" while refactoring: git diff --exit-code --quiet Testing/; if (( $? )) then; echo "FAIL"; else; echo "OK"; fi
Trying to do something like #TDD with #jq
I'm using Golden Master technique and I've committed the expected output to git.
This is "assert all remains well" while refactoring:
git diff --exit-code --quiet Testing/; if (( $? )) then; echo "FAIL"; else; echo "OK"; fi
jbrains, 3 months ago Zero-button/Continuous testing: find . | entr -s 'echo "\n\n" && date && git diff --exit-code --quiet Testing/; if (( $? )) then; echo 'FAIL'; else; echo 'OK'; fi'
Zero-button/Continuous testing:
find . | entr -s 'echo "\n\n" && date && git diff --exit-code --quiet Testing/; if (( $? )) then; echo 'FAIL'; else; echo 'OK'; fi'
lewiscowles1986, 3 months ago @jbrains is this related to https://mastodon.social/@jbrains/111846184994801060 at all? When you use inter-process testing, how much control over the environment are you looking for? For me magic environment vars affecting behaviour are something I want to not have when executing a sub-process Thinking env -i PATH=$PATH bash -c "${yourcommand}" I use bash or $SHELL because it adds some minimal expected environment; but not much
@jbrains is this related to https://mastodon.social/@jbrains/111846184994801060 at all?
When you use inter-process testing, how much control over the environment are you looking for?
For me magic environment vars affecting behaviour are something I want to not have when executing a sub-process
Thinking env -i PATH=$PATH bash -c "${yourcommand}"
I use bash or $SHELL because it adds some minimal expected environment; but not much
Add comment