New answers tagged unit-tests
Since there was no tool to do what I needed, I wrote one. https://github.com/edsonmedina/php_testability
After reading the answers I feel this is an important distinction to point out. 'Unit testing' and 'Checking parameters in your code' are two distinct things. This is checking the parameters. My method checks there aren't null values before it does something invalid. It documents assumptions you made in the method, enforces them, and fails fast. It's thing ...
Here's my interpretation (caveat - I could be wrong): Key sentence from the article: The keyboard handler parses the mode and energy level specified by the operator and places an encoded result in another shared variable, the 2-byte mode/energy offset (MEOS) variable. This corresponds to the code: repeat fetch parameter output parameter point to ...
The last paragraph of the article is not clear. Does it explain how the bug was resolved or does it refer to code added before the tragedy occurred and the bug was found? One interpretation of the code in the red box is that it is the fix to the race condition, ie the fix for the bug.
Take a look at SonarQube. It has some good code complexity metrics. Since code complexity generally translates to test-ability, it will give you a good idea which areas of the code need refactoring. It also gives you some metrics on unit-test coverage. I find the historical aspect of this metric to be helpful. As code is added and/or refactored, I like ...
Top 50 recent answers are included