We started this chapter with the need to add transaction support to our application code to support the ease of writing programmer tests. With transaction support, we don t leave persistent garbage in the database. Changing to use transaction support at this point may seem like a lack of foresight on our part. However, if the customer decided not to provide Add/Delete Review functionality through the Web service, we would not have had to do this. It turns out, however, that using transactions simplified the programmer tests so much that we might be inclined to use this approach in the future, even if we did not have update functionality.