Recently I ran into some problems with tests that could not easily be run in an automated manner. In the spirit of a glass half full, I am trying to decide if manual tests are partially useful, partially useless, or totally useless. The kind of work that I do, laboratory automation, scientific instrumentation, medical devices, [...]
Archive for the ‘mocks’ Category
A Test That Isn’t Automated Is a (fill in the blank)
Posted in MbUnit, mocks, TDD, testing on October 21, 2010 | 2 Comments »
TDD with C++
Posted in mocks, TDD, testing, Unit Testing on September 6, 2010 | Leave a Comment »
I know, it is 2010, and doing TDD with C++ probably isn’t trending too high on anyone’s hot topics list, but after a 8 year hiatus I find myself doing some Agile consulting with an embedded systems team that is using C++. At first I was concerned about the transition. What was I going to [...]
“When do you write your tests?” This is a question that I have been putting to developers lately and the answers I get back sometimes surprise me. I still hear a lot of people say they are writing their tests after the majority of the code is written. These are people who, by and large, [...]
PyCon on the Charles – Part I
Posted in mocks, Python, testing, Unit Testing on January 21, 2010 | Leave a Comment »
I have been doing some work with Python the last few months and recently joined a Python Meetup group in Cambridge that had a meeting last night at Microsoft NERD. The purpose of the meeting was a chance for some people who are presenting at PyCon to do a dry run on their presentations. The [...]
Rethinking the C# using statement
Posted in C#, mocks, nmock on February 11, 2008 | 2 Comments »
I’ve typically used the C# using construct to wrap an instance on an object that has a short lifetime and requires a call to Dispose. The using keyword hides the need to call Dispose explicitly and avoids having to use a try-finally to ensure that Dispose is always called. One example of a class that [...]
