# About Test Idea Catalogs

You can develop a standard set of tests for a specific type of object (or risk) and reuse the set for similar things in this and/or later products. Marick (1994) suggested that testers develop these types of lists and called them test idea catalogs.

Having a good catalog to reference should be part of every software tester + developers toolbox. The following are meant to help with specific and more generalized testing, to provoke ideas for finding failures.

## Other Catalogs:

* [Chapter 3 of Lessons Learned](http://www.testingeducation.org/BBST/testdesign/KanerBachPettichord_Lessons_Learned_in_SW_testingCh3-1.pdf)
* [Falsehoods Programmers Believe About Names](http://www.kalzumeus.com/2010/06/17/falsehoods-programmers-believe-about-names/)
* [Marick's Short Catalog of Test Ideas](http://www.exampler.com/testing-com/writings/short-catalog.pdf)

## Resources:

* <http://sce.uhcl.edu/helm/rationalunifiedprocess/process/workflow/test/co_tstidsctlg.htm>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://guides.kenst.com/misc/about.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.