26 réponses à ce sujet

[fkirenicus]

According to standard testing theory (I should know this, I am a software test manager) the developer makes a mistake that introduces an error in the code, which can turn out to be a bug if the program halts or does not intend when run and thus causes a failure.

So Bor1, what you said is not true if we're looking at semantics - a bug isn't the result of user actions, but failures in most cases are.
Note that an error/mistake in the code not always needs to manifest itself in a bug that causes a failure in the software when run, though.

Modifié par fkirenicus, 03 décembre 2009 - 10:08 .

[Bor1]

totally agree with you, colleague  
I mean - any bug can be classified as "user action" (application launch - user action) and for an end-user bug is reaction (in most cases) on action, but in the reality the problem inside of code (sometimes software/hardware compatibility problems occurs also)... 
some bugs can be found by using code-testing another only through manual testing...
In any reason this is another theme - we can continue via PM if you want

Modifié par Bor1, 03 décembre 2009 - 10:58 .