It depends on the type of software.
If it’s a website you’re building, you’ll be checking for availability on the web, and that all the tags work.
If it’s a piece of software to control a machine, you might be doing different procedures.
There is a whole area within engineering dedicated just to “testing” whether software works or not, intuitively enough, it’s called “software testing” or “software quality assurance”. It is an actual job, with high demand for all companies doing any type of software.
I personally think you can never ABSOLUTELY be sure that it WORKS ALL THE TIME.
There are always limitations. Maybe at a given time, under some circumstances etc. but the world and most importantly people just change too fast to be able to claim more than that.
However, you can assure that your software works according to your or even more importantly to its users needs. And the key to that lies in testing indeed. Test early (some would even say before you write a small piece of your software you should write its tests first) and test constantly…
If you’re interested in testing a very nice book I just came across introduces it through fantasy stories is this: https://www.dragonsout.com/
And if you’re maybe considering learning some programming language, a great site that teaches you with a test-first mindset is this: http://exercism.io/
Comments