Microsoft.Net Testing

Editorial / Best Answer

Answered by: sarega99

View all answers by sarega99

Member Since Mar-2010 | Answered On : Sep 26th, 2011

The obvious answer is when a particular functionality does not work,then it becomes a functional defect. For eg. When a wrong date can be entered for eg.when only today's date can be entered and system allows to enter any past or future date,then is is a functional defect. Another example would be when the system crashes (a show stopper) that would be a functional bug.

Editorial / Best Answer

Answered by: kurtz182

View all questions by kurtz182   View all answers by kurtz182

Member Since Nov-2009 | Answered On : Dec 11th, 2009

Generally, when an application is partially running, it is no longer in a stable state suitable for testing.  Reboot your system (or reinstall a clean image of the build) and attempt to reproduce the issue, paying particular attention to the steps required to get there. Document your findings in a defect report.  Don't forget to include screen shot(s). If error messages are returned by the application during failure, include this in your report.

If you want to determine the source of the existing defect, then check the Error Logs on the local and/or serving computers.  The error messages in these logs will often describe the nature and source of the problem. Testers can set the Event Filter of this log if they know the event type or session they wish to examine.  Event Details provides an exception stack trace that can be included in the defect report.