Homemade CLI Tools
Go is great! We all know that. I spend most of my coding time on the back-end of the services we build. For many years, before I moved to Go, I used to create my tools as a combinations of various scripting languages - not excluding PHP! Most of it was run by Bash that was executed as a cron job, systemd service or manually as a one-shot executable. I must say, Bash is not as bad as many seem to think.…
Automated testing in a build pipeline
A testing mindset with its' scripts would be incomplete if we did not put them to good use. Ideally, tests should be run every time we intend to share our code with anyone - be it our team or the whole world. It is a tech lead’s wet dream to work in an environment where every dev thoroughly tests their solutions. As this might be impossible, we can have the next best thing.…
Multiple tests run in bulk using Bash
Having briefly explained what a test is we can come to an inevitable conclusion that having only a single test is never enough. We usually write a lot of them and it is useful to group them. Assuming that the tests we are using conform to the contract of returning proper exit statuses, the whole group can technically be treated like a single test. Let’s put them inside a tests.sh script:…
What is a test in software development?
When joining a new project (and maybe even in a previously unknown programming language) we can get overwhelmed by the complexity of the test suites. Sometimes it can even be a nightmare to run them, not to mention understand what is going on. There are lots of levels the tests can be run on. Let’s start with the basics. Anything that checks if a requirement is met is a test. How do we apply this mindset in real life?…