Testing Guide
Back to Kenst
  • Home
  • Data Catalogs
    • Fixed Point
    • Floating Point
    • Integers
    • Phone Number
    • Strings
    • Zip + Post codes
  • Error Catalogs
  • Test Strategy
    • HTSM
  • Exploratory Testing
    • Writing Exploratory Charters
  • Test Design
    • Automating
    • Domain Testing
    • Functional Testing
    • Regression Testing
    • Security Testing
    • Unit Testing
    • Test Techniques
    • Test Oracles
    • Quicktests
  • Misc
    • Examples of Testing Portfolios
    • Stopping Rules
    • Testing Folklore
    • Mobile
    • About Test Idea Catalogs
    • Bug Reporting
    • Test Reporting
Powered by GitBook
On this page
  • Software Error Catalogs:
  • Security Catalogs:

Was this helpful?

Error Catalogs

PreviousZip + Post codesNextTest Strategy

Last updated 4 years ago

Was this helpful?

You can use existing error catalogs or develop your own.

To use an existing error catalog:

  1. Find a defect in the list

  2. Ask whether the software under test could have this defect

  3. If it's theoritically possible the program could have the defect, ask how you could find the bug

  4. Ask how plausible it is that the bug could be in the program and then how serious the failure would be if it was there

  5. If appropropriate design a test or series of tests for bugs of this type

Software Error Catalogs:

Security Catalogs:

Common Software Errors from TCS, 1993
National Vulnerability Database
Common Weakness Enumeration