Skip to content

Introduce "Flaw" as a catch-all for what we've called "Discrepancies" #140

@samm82

Description

@samm82

In #137, @JacquesCarette came up with the term "flaw" to refer to any instance of something being "wrong" with software testing terminology. We clarified our path forward for defining this set of terms in #151.

  • Use "flaw" in TeX files
  • Use "flaw" in LaTeX macros
  • Use "flaw" in file names
  • Use "flaw" in Python variable names
  • Use "flaw" in Tex labels
  • Move Table 4.3 to Terminology and split into its orthogonal parts
  • Define "singular" versions of kinds of flaws (so that we can say "definition flaws" with the hyperlinked macro/flaw ref without having to say "flaws with definitions")
  • Use "inconsistency" as a synonym for "flaw" when comparing multiple sources instead of "discrepancy" (Proposed Taxonomy of Flaw-related terms #155, Thesis Meeting | Mar 3, 2024 - 2:30pm - Teams #156)
  • Remove "in-depth" research into why "flaw" is a good term to use (maybe as a footnote). (Thesis Meeting | Mar 3, 2024 - 2:30pm - Teams #156)
  • Explain the rationale behind the term "flaw" by reverse engineering what it means for something to be "wrong"
    This will also give us more complete criteria when making recommendations. Currently, the 'manifestations' seem to provide good anti-criteria…
  • Include a brief summary of this terminology, likely in the introductory chapter, emphasizing that "flaw" is the general term

Metadata

Metadata

Assignees

Labels

documentationImprovements or additions to documentationenhancementNew feature or request

Projects

Status

Done

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions