We all have been in this kind of situation: someone in the team states that a feature is done but in reality there is that little thing to figure out and the coding is completed the day after. Why is that? Because every person has a different definition of done inside his mind. How can … Continue reading ALM DOs & DON’Ts – Definition of done
A unit test is a runnable piece of code that verifies that another piece of code (called production code) does what it is supposed to do. A unit test has many characteristics and one of the most important is that a single unit test must verify one and only one thing. If a unit test specifies more … Continue reading ALM DOs and DON’Ts – Unit test
The database is a critical part of our application. If we deploy version 2.0 of our application against version 1.0 of our database, what do we get? A broken application. And that's why our database should always be under source control right next to our application code.
We all know the practice of continuous integration. One of the common pitfalls about CI is that the build status is not monitored and not treated as one of the top priorities for the team. A healty/green status of our CI process means that our code is in a good shape for what our automated … Continue reading ALM DOs and DON’Ts – CI builds status