| || |
Performance focussed unit testing
We are trying to implement additional criteria to our developers unit testing of an ASP.Net application, so that we flag performance issues earliar.
So far I have come up with the following guidelines. Is there anything else that could be added?
Create explain plans and tuning queries. Ensure that total cost is low or as expected. Submit SQL for performance review by oracle expert.
Ensure Viewstate size is kept reasonable and does not grow.
Reasonable response time for functionality should be measured. Any 'bad' timings should be flagged as an area for technical testing focus.
Breakdown tests should be executed to detail where processing time is being spent.
[ 08-25-2004, 08:15 AM: Message edited by: mongoose ]
Re: Performance focussed unit testing