Mock the Clock
Take Time to Throttle Testability
Your unit test should have no dependencies on anything external, you know that already. So you try not to read any files or connect to a database server. But what about time? Recently we had some unit tests that failed during nightly build due to daylight saving. Suddenly the distance between two days was 23 hours.
But it doesn't stop at unit tests. System tests, too, may depend on time.
You should have a strategy for how your system perceive time. Read on.
But it doesn't stop at unit tests. System tests, too, may depend on time.
You should have a strategy for how your system perceive time. Read on.
Understanding a System
What do you do to understand?
I teach a course on System Architecture. It is a three-day course attended by experienced developers who want to go further in some respect.
What strikes me most is that the majority has never read any architecture document. Since writing such documents is one of the main topics of the course, I have a long road for them as they haven't read any.
So, when you are faced with a system that you are about to change, how do you go about to understand it?
What strikes me most is that the majority has never read any architecture document. Since writing such documents is one of the main topics of the course, I have a long road for them as they haven't read any.
So, when you are faced with a system that you are about to change, how do you go about to understand it?