First, at the suggestion of one of my friends who now works at SmartBear, I’m going to experiment with creating audio of my post going forward. Obviously this will lend itself to some of my post more than others, but I think it is worth experimenting with.
Those of you who’ve been with me since the early days remember that I use to produce YouTube videos occasionally. I haven’t done that in a while because the post production process for videos takes so long. I’m hoping that I don’t run into the same problem with producing audio.
Continue reading “Don’t Comment Out That Test”
Podcast: Play in new window | Download
So far we’ve been talking about creating test as part of the development process. If all you ever used those test for was to make the design of your systems better, you would already be far ahead of most of your peers.
But now that we have test, we might as well get as much mileage out of them as possible. To do that, we are going to run our test every time we make a change.
Continue reading “Make Your Test Work For You”
Many people believe that implementing Test Driven Development means that you need to have a test for every line of code in your system. When they start thinking about TDD in this way, they start to feel overwhelmed and quit before they even start.
I know I did.
In fact, I’ve seen suggestions on places like StackOverflow that suggest as much.
But there is code in your application that you shouldn’t bother to write a test for.
Continue reading “What Not To Test”
One problem we often have when performing application test is that if we are testing applications that modify the database in some way, we can’t test without modifying the database.
In an ideal world, one way you could deal with this issue is to create a test database that has known data. But even then, you have to go through the effort of setting up the data prior to each test.
Continue reading “Automated Web Application Functional Testing”