Posted by Albert Gareev on Oct 24, 2008
Reference page: Error, Bug, Issue, Incident More often than other developers, about incidents hear product managers, customer support techs, and product support programmers – whenever an end-user experienced and reported a problem with the software product. However, incident is not necessary a bug. It might be caused by a variety of reasons, like following: Configuration […] ...
Posted by Albert Gareev on Oct 21, 2008
Reference page: Error, Bug, Issue, Incident The notable comment about word “issue” used in software testing context is that it’s often referred as a problem or an obstacle – which is uncommon meaning. Generally, an issue is defined as “something that is sent out or put forth in any form” (Dictionary.com). Wikipedia explains this discrepancy with […] ...
Posted by Albert Gareev on Oct 16, 2008
Reference page: Error, Bug, Issue, Incident Let’s start from definitions. A software bug is the common term used to describe an error, flaw, mistake, failure, or fault in a computer program or system that produces an incorrect or unexpected result, or causes it to behave in unintended ways. Wikipedia.org “An unwanted and unintended property of […] ...
Posted by Albert Gareev on Oct 14, 2008
Reference page: Error, Bug, Issue, Incident Let’s start from definition. “Error – a deviation from accuracy or correctness; a mistake, as in action or speech.” Dictionary.com Indeed, in the most circumstances when it was referred as “error” it was a mistake, as in the examples below. Typo, or syntax error in the programming code Logical […] ...
Posted by Albert Gareev on Oct 10, 2008
For Test Automation, Functional Decomposition is a test flow analysis and test design technique. And yet somehow it is often confused with structural programming. Decomposition of Test Flow Applying Functional Decomposition technique in Test Flow Analysis means splitting (decomposing) a testing scenario into its constituent parts, that are logically complete and data-wise isolated. Some of these parts […] ...
Posted by Albert Gareev on Oct 05, 2008
“We have a build error…”, “You need to investigate that incident…”, “Today I fixed two bugs…”, “We already saw this issue in the last release…”. Are you used to hearing that? Have you ever wondered why there are so many words used talking about software problems? So did I. Looking back to my 15 years being in […] ...