[french] LE BLOG

Marco Behler's riffs on programming, IT culture and the way software projects are made.

An intro: How do I test my software?

There's a lot of discussion going on in the software community on "testing". (See for example herehere and here). We think there's too many superstitions and assumptions. Very little of this helps in your day-to-day work and leaves you still wondering how you reliably and automatically test, for example, that crazy sql query, your UI or that complex batch job.

Update: As reddit commenter flussence pointed out our numbers here aren't very reliable. So if you want to compare things some may suggest that running

sync; echo 3 > /proc/sys/vm/drop_caches
before each time taking is a must. What we aimed for in this article though is to show two simple ways of speeding up an arbitrary build. Whether our suggestions are applicable to your given use case is something you have to see for yourself.

Are you also dreading your slow CI jobs? A build+test cycle of a couple of minutes sounds like a far distant dream. Reality is, after each check-in you can grab a coffee and watch the first half of the Godfather until your test results trickle in from Teamcity or Jenkins.

(Note: You can find fully working code examples for this article on our Github account)

Newer Posts