Test Notes

I don't make software; I make it better
posts - 78 , comments - 60 , trackbacks - 616

My Links

News

  

Please Note
The information in this weblog is provided “AS IS" with no warranties, and confers no rights. This weblog does not represent the thoughts, intentions, plans or strategies of my employer. It is solely my opinion. Inappropriate comments will be deleted at the authors discretion.


Google 

Groups
SoftwareTesting
Browse Archives at
groups.google.com



  Page Loads:

Technorati Profile

Click for Hyderabad, India Forecast

Tag Cloud

Archives

Post Categories

Friend's Blog's

Groups

Sites

Testing Blog's

August 2004 Entries

Pairwise Testing

We can save time and effort and find bugs efficiently by testing variables and values in combination.  Read this  http://www.developsense.com/testing/PairwiseTesting.html

Posted On Friday, August 27, 2004 3:38 PM | Comments (2) | Filed Under [ Software Testing ]

Now I got a shorter URI for my blog
http://testing.mvpblog.com/

Posted On Thursday, August 26, 2004 5:19 PM | Comments (3) | Filed Under [ Personal ]

The term “bug” is not very precise
Error: mistake made by the developer; located in people’s heads. Fault: an error in a program. An error may lead to one or more faults. Failure: execution of faulty code may lead to one or more failures. Failures are found by comparing the actual output with the expected output. Many people still call it a “bug” ......

Posted On Friday, August 20, 2004 8:24 PM | Comments (4) | Filed Under [ Software Testing ]

Testing is a state of mind
“If our goal is to show the absence of errors, we will find very few of them” “If our goal is to show the presence of errors, we will discover a large number of them” --by Mayer, 1979 ......

Posted On Friday, August 20, 2004 8:23 PM | Comments (6) | Filed Under [ Software Testing ]

Why an error found after release costs more?
Here are the reasons 1st cost: developing program erroneously 2nd cost: system has to be tested to detect the error 3rd cost: wrong specs/code removed, correct specs/code added 4th cost: system must be retested ......

Posted On Friday, August 20, 2004 8:22 PM | Comments (1) | Filed Under [ Software Testing ]

Bug Triage Meeting – Severity & Priority
"Triage" is a medical term. It refers to dividing wounded or sick people into three categories: those who will die no matter what you do, those who will recover even if unaided, and those who will recover only if aided. In a situation where there's too much to do, you must concentrate on the third group. Bug Triage Meetings (sometimes called Bug Councils) are project meetings in which open bugs are divided into categories. The most important distinction is between bugs that will not be fixed in ......

Posted On Friday, August 20, 2004 3:02 AM | Filed Under [ Software Testing Testing/QA-FAQ ]

Powered by: