Tdd

Obeying to the TDD (Test Driven Development) saved me a lot of time so I decided to write about it. It nicely shows the real-life advantage you can get from following TDD. Now, to keep it short - few days ago I was writing some business logic that did some audit recording changes. For the sake of brevity imagine it was something between those lines: public void recordAudits(Data data) { if (data.someCondition()) { recordAudit(auditA) } else { recordAudit(auditB) } Now, the current unit tests were in-place and were using some utility class for finding if the expected audits were recorded: ...

When you have some non-trivial boolean statement used in if like: private void evict(Data data) { // ... if (data.getDate() >= MATURITY_DATE && data.type == DataType.UNDEF) { // do the eviction } } To make it easier to read and maintain, it’s a good idea to extract it to a local variable or method: private void evict(Data data) { // ... boolean isEligibleForEviction = data.getDate() >= MATURITY_DATE && data.type == DataType.UNDEF; if (isEligibleForEviction) { // do the eviction } } or ...