36 Heuristics

• Customers
• Information:

  The more information we have, the smarter we will test.

  • The design is similar to other products we already know.
  • The technology on which the product is based is well understood.
  • Dependencies between internal, external and shared components are well understood.
  • The purpose of the software is well understood.
  • The users of the software are well understood.
  • The environment in which the software will be used is well understood.
  • Technical documentation is accessible, accurate, well organized, specific and detailed.
  • Software requirements are well understood.
• Developer relations
• Team
• Equipment & tools
• Schedule
• Test Items
• Deliverables
• Structures
• Functions
• Data
• Platforms
• Operations
• Time
• Capability
• Reliability
• Usability
• Security
• Scalability
• Performance
• Installability
• Compatibility
• Supportability
• Testability
• Maintainability
• Portability
• Localizability
• Function testing
• Domain testing
• Stress testing
• Flow testing
• Scenario testing
• Claims testing
• User testing
• Risk testing
• Automatic testing