Software bugs

In Kate Rhodes’s Best Practices for Web Developers, she addresses best practices for triage:

…lets be honest with ourselves. We’re actually ok with some things going “boom”. If we weren’t we’d be working for NASA. Every other development house I know of regularly releases software with bugs in it. As long as nothing too important breaks and nothing breaks in a way that leaves you looking like an idiot there’s a good chance you’re willing to live with it, for a while at lest. So, now that we’ve admitted the truth to ourselves, we can start triaging our app.

Popularity: 40% [?]

OpenQA is the home of several open source testing tools, notably Selenium, for automated testing of web applications in a number of browsers, including the major ones.

Popularity: 95% [?]

Luis Villa writes about Infotopia, information-gathering, and software QA, comparing QA problems in open source and proprietary software:

Quite simply, the big problem in QA is getting information about the state of the software out of the software and into the hands of developers as efficiently as possible.

This has three aspects: creating the information, getting it in the hands of the QA teams, and then filtering it into a form that is useful for developers to work on. Traditional QA has a very hard time getting the information… In contrast, open source QA has a whole ocean of information from the legions of volunteers willing to run pre-release code; the trick is to tap into that water without drowning in it.

Popularity: 74% [?]