One of the biggest challenges in unleashing the power of unit testing is getting good code coverage. Most of the time, especially when teams are just starting out with Test Driven Development, unit testing usually gets in the way. A lot of people (I succumb to this syndrome sometimes) add tests after they develop code. The audacity! Some people just don’t unit test at all- especially when struggling with mocking a dependency, like a database or the HttpContext object. And forget about finding more than one unit test for functions- you already have one for a function which passes- so you’re done, right?
Yearly Archive for 2008
There are going to be times when you want to allow a user to enter multiple copies of a single form on a web page. This frequently happens when adding items to a list- like products in a shopping cart or tasks in a task list. You want the user to add as many “items” as they want to the list, then save the entire list at once.
Note: This is part of a series on hiring software developers. See articles tagged with interview for the series. I needed to break the in house interview post into two parts. This part focuses on open ended questions.
Managing Complexity in the UI
As everyone knows, the more dependencies you have in a system, the harder maintaining that system is. Javascript is no exception- and orchestrating actions across complex user interfaces can be a nightmare if not done properly.
I found this when going through some code:
//I have no idea what the following code does
//but the ui seems to function better without it
//except for when it crashes
