https://www.slideshare.net/andreicontan/daniel-billing-exploring-the-security-testers-toolbox

• A Risk Catalog for Mobile Applications
• Common Software Errors
• A Taxonomy of E-Commerce Risks and Failures
• Bug taxonomies: Use them to generate better tests

• https://peter.sh/experiments/chromium-command-line-switches/
• https://developer.mozilla.org/en-US/docs/Mozilla/Command_Line_Options

There are common fields like:

• Date fields
• Money fields (validation, error messages, accepted input, etc.)

Should be data-types, I think. Doesn't just apply to input fields, any variable with this data-type.

Create a list of possible information objectives

• Turn this into a website
• Try using GitBook

Chapter 15 has half a dozen or so different bug taxonomies. They are old and small but I think that just makes it easier to use those as a starting point for a separate bug directory...?

1. Locate zip codes with exceptionally long city names
2. Long city names around the world (maybe excluding zip codes)
3. Weird country names

• What are style guides? A guide to help people test their changes by being able to reference a standard
  • Frameworks and Style Guides seem to be popular ways to phrase and organize consistent approaches to how people work without the baggage (and inflexibility) of being standards
  • Standards or Defined Processes give off this aurora (and sometimes dictate) the way in which an individual should work and any deviation (even correct) is a violation of such standard

• A Checklist should be simple, but I like to reference many of the mnenonics when I test
• Add links to templates for help during test design.

• Add to the README
• What's the difference between a catalog and a guide? Why both?

Add guide for doing unit tests

https://github.com/ckenst/images_catalog

• A customized resource that I can edit and publish to git
• Should be accessible from the web (maybe editable from the web as well)
• The idea is a wiki or GitBook
• What are my options?

1. What other sources of information, data can we use?

• UI design test ideas
• Boundary test ideas
• Value overflow test ideas
• Invalid operation test ideas
• Modified value test ideas
• Sequence test ideas
• Error handling test ideas
• File system test ideas
• Load tests ideas
• Quicktests

The TOC lists several different catalogs to be found in this book.

https://dojo.ministryoftesting.com/dojo/lessons/mobile-app-testing-mnemonic

catalog of analytics / things that might help us better understand our customers usage

• These are different though, because these are catalogs in and of themselves

• Organize around catalogs vs guides
• Organize catalogs around risk
• How do we use the catalog?

• Remove TODO file, manage here
• Remove contribute section from README