Archives for the 'Code Integrity' Category
Bug Fix Time not a good metric
After a few weeks using the BugFixTime metric, I found that metric too hard to understand and leaves the developer and managers clueless to what that have to do to fix the metric.
We have done some internal thinking and some feedback and have created the next generation of this tool built to help teams develop […]
Measuring Effective Unit Tests
What is an effective unit test? A good unit test (via Jeremy Miller) is
Atomic
Independent & Isolated
Intention Revealing
Easy to Setup
Runs Fast
But how do we know that the test is effective? The biggest value of unit tests come when they fail. When a test fails, and we fix it, we have saved […]
Measuring Code Integrity
I have been pondering this for quite some time now. How do we measure the code integrity. Code Coverage doesn’t really do it, and the number of test or test density also doesn’t.
I proposed to go back to the commercial essence of unit testing and bug slaying. In a team that doesn’t unit test, […]
Big Steps to Code Integrity
Typemock is making big steps towards its goal of code integrity. Code integrity is what we consider the new paradigm of writing software. Moving the responsibility of code-correctness back to the developers. It is too easy to get sloppy and to leave it to the QA to find our bugs, thus developing without integrity and […]
Does you code have integrity?
I have been talking about integrity management, but the word integrity actually comes from the technical condition of being whole. That is why in star trak we hear that the Enterprise’s hull integrity is failing. The ship is not complete. When a car leaves the manufacturing company, it gets stamped 100% integrity, meaning that […]
Subscribe!
RSS 2.0