Effort Estimating for Test Automation Projects

By Babu Narayanan
Aug 18, 2005

Summary: "The subject of software estimating is definitely a black art," says Lew Ireland, former president of the Project Management Institute. As you know, estimating is more of an art than a science, and inherently more prone to the negative aspects of human biases. So bare with me, if am awry in my estimation exercise. These are the lessons learnt out of my experiences which describes in detail the following key areas for effort calculation:
Candidates for test automation.
Factors that affects test automation estimation.
Grouping steps to determine complexity.
Framework design and estimation.
Scripting effort estimation.

Tim Weaver : NUnit with ASP.NET Context

NUnit with ASP.NET Context

Recently a bug was found in one of our components. Okay, so finding a bug isn't unusual, however what made this one stand out was that the component in question had over 70% code coverage with NUnit tests and it still wasn't found. Turns out the bug was related to the very small percent of code that relies on ASP.NET Context. The code isn't covered by our NUnit tests because frankly it is really hard to deal with ASP.NET context through unit tests.

I decided I wanted a way to get better coverage. Specifically I wanted to execute the code dependent on ASP.NET context. A quick google search turned up a few examples of how other people have tackled this. I took some of the examples I found and extended them to meet my requirements.

Ramadan - What is it?

  Ramadan is one of the most important and holy months in the Islamic calendar. It is a time of fasting, prayer, and spiritual reflection fo...