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

October 2004 Entries

Bug Reporting Best Practices
Here is the excellent post written by Marie Hagman. This is one of the post where you can find comprehensive details about “how to file a good bug report”. Update the post a bit to make more generic. Which Bugs Get fixed? To make the most impact on the product you want to spend the most time on the issues that are most likely to be fixed. Bugs that get fixed: Affect many customers Are embarrassing or do not convey professionalism. Ex: fit and finish bugs Are easy to fix Bugs that less ......

Posted On Wednesday, October 6, 2004 12:33 PM | Comments (7) | Filed Under [ Software Testing CSTE ]

'Best practice - daily investigation of the test case failures'
" The end goal we’re trying to achieve is that every day we have a mapping table between failing test cases and relevant bugs. " - By Gunnar Kudrjavets -  good stuff, read it

Posted On Friday, October 1, 2004 12:01 PM | Comments (0) | Filed Under [ Software Testing ]

Powered by: