I’m a firm believer in the phrase: “What gets measured gets managed.” When it comes to unit testing code coverage is something we can use to measure how much of our code is under test. By no means does this mean that the code that is under test is actually covered by valid tests that…
Category Archives: Testing
Excluding Integration Tests from your Automated Build
A simple tip to exclude certain tests from running during your automated build. In this scenario we have a bunch of tests inside of a particular DLL. Inside of these tests we have a folder that is for “integration tests”. These tests are run usually once a day in a nightly build and are also…
Integration Testing
Integration Testing Purpose: Testing how the layers/tiers/objects integrate with each other. When we’re unit testing, we’re testing a single unit of code. We’re testing to see if an addition operation results in what we expect it to. Does five plus five equal ten? Does this complex calculation f(x) result in y when x = 5?…
4 Common Follies Made In Unit/Integration Testing
I was having a discussion with a colleague last week and we got on the topic of unit testing. What unfolded is what stemmed this post… It started like this… Colleague: “There is no need to test getter’s and setter’s in a property, because ‘I know they work’.” Me: “WHOA WHOA WHOA!! You know they…
Unit Testing – It’s not what most of you think …
Unit Testing Purpose: To test an individual unit of code to ensure that it is working properly. This is where the most confusion lies, so I’m going to focus the majority of the beginning series on this area. Possibly to the effect of a few posts. Normally you’ll hear a developer say “I have unit…
