Skip to content

Implement Additional Feedback on Methodology Section #143

@samm82

Description

@samm82

This is mainly a place for me to organize my thoughts/next steps and will be filled in as I go.

Following #129, the following changes/sections still need to be made:

Methodology

  • Succinctly describe the goal of our methodology:
    Our main goal is to produce a complete, correct taxonomy of software testing terminology. However, we cannot do this without understanding its current state. Therefore, we need to document software testing terminology, along with its flaws, which will result in a big messy table of how terms are currently used. The flaws in these data can then later be resolved by analyzing how and why they emerge. For now, we document the current (messy) state of software testing terminology by:
    (see Thesis Meeting | Feb 18, 2024 - 2:30pm - Teams #148 and this comment)
  • Elaborate on stopping criteria (both ideal and our actual one)
  • Add an example workflow for how we would record the information about a specific test approach
  • Omit analysis and recommendations from methodology overview, since these come later (discussed in Thesis Meeting | Feb 18, 2024 - 2:30pm - Teams #148)

Procedure

  • Move general discussion on procedure to intro section (see Pull Terminology out to its own chapter #146)
  • Evaluate existing content, ensuring it makes sense to be here (and have its own subsection)
  • Elaborate on decision-making procedures
    • Elaborate on the significance of the multiple documents for tracking information (I can't find any mention of this in the reviews of this chapter, and I think I outline these documents well enough, so I'm considering this complete)
    • Describe methodology for identifying implicit information more "algorithmically", perhaps using a flowchart, to show that it is "based on the text of the sources" (pending Dr. Smith's review of Terminology section #185)
    • Elaborate on "precedence" for a quality being a test approach
  • Separate results of procedure (e.g., "we found vague ones") from the procedure itself - maybe move to scope appendix?
  • Elaborate on conclusions from Fig. 3.3 (results of investigating undefined terms)

Minor Issues

Discussed in #160

  • [sic] in "Keyword-Driven Testing"
  • citep vs. citet
    • addTextEx
    • citet for source lists?
  • "none given" vs. "none found"
  • What to do about things that are already done? (e.g., "p.~12")?

Sub-issues

Metadata

Metadata

Assignees

Labels

enhancementNew feature or requestreviewRequest for (or response to) review

Projects

Status

Done

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions