# open issues weighted for priority / # closed issues weighted for priority?
Company processes/methods must meet a specific standard (ex. ISO 9000)?
But does a piece of software have quality if a team follows a rigid set of processes, tests it thoroughly to make sure it has no bugs, but then on release nobody wants to use it, or it fails to a competitor?
Testing
Prevent regressions
Unit tests
Continuous integration
User/customer testing
A/B tests
Usability testing
Find new bugs
Functional testing
Exploratory testing
Black/Gray/White box testing
Performance testing
White hat hacking
Testing
Prevent regressions
Unit tests
Continuous integration
User/customer testing
A/B tests
Usability testing
Find new bugs
Functional testing
Exploratory testing
Black/Gray/White box testing
Performance testing
White hat hacking
Software QA Testing
Confirm that the product works as expected
Then break it
How to break software
Permute inputs and outputs
Orthogonal array techniques help reduce redundancy and help testers find bugs sooner
Act in bad faith
Don't assume users are going to do the right thing
