How many times as developers have we made list of things we needed to work on. Most of the time they are 'tasks' in some sort of task management system. However, we do not have one of these such systems at work. So I decided to use 'ignored' tests as my tasks.
I did this in 2 ways:
- As I was creating the various objects and methods I started creating tests that had the only contained Assert.Ignore("SomeMessageHere"). In the body of the method added a description of what needed to be done.
- I also created a list of other tasks that I needed to do (ie finish setting up CI, determining where to get various config information, etc). These tests were also simply Assert.Ignore.
I decided to do this because I figured that seeing these tests in my list over and over again would be a good way to remind me of what needed to be done.
I set these to be Ignores in place of Fail because I don't want these tests to cause my CI process to fail.
Anyway, for some reason it had never occurred to me that tests could double as a 'To-Do' list, but it works.
Till next time,
03-21-2008 7:28 PM