Print Page | Close Window

BUG FATAL

Printed From: One Stop Testing
Category: Software Testing @ OneStopTesting
Forum Name: Test Plans @ OneStopTesting
Forum Discription: Discuss, Learn and Prepare better and better Test Plans for yourself.
URL: http://forum.onestoptesting.com/forum_posts.asp?TID=5791
Printed Date: 24Nov2024 at 5:43am


Topic: BUG FATAL
Posted By: mangai166
Subject: BUG FATAL
Date Posted: 08Jun2008 at 10:49pm
WHAT WE SHOULD EXPLAIN 4 THE QUEST...bug FATAL U HV CME ACROSS


Replies:
Posted By: lawrence
Date Posted: 09Jun2008 at 8:11am
If you had come across 'bug fatal', then explain it. Otherwise simply say 'I have not come across bug fatal so far'.

Posted By: cprasenjit26
Date Posted: 21Jul2009 at 8:18pm
Fatal error handling is patchy and flaky. It's very easy to throw a fatal error, put up a message box, and then receive a Windows message containing yet more socket data. The MessageBox message loop then dispatches that message automatically and the back end is called reentrantly. Chaos ensues. Solution: the fatal error behaviour should be much more robust. Close all sockets the instant a fatal error occurs; also set some global flags that prevent action messages from having any back end effect.
-------------------------------------------------------------------------------
http://softwareqatestings.com - Software Testing


Print Page | Close Window