Chiosa
Research collection

Software & Code

Research on Software & Code: explanations, evidence, limitations and connections between papers.

22 results

  2. Guided lessonSoftware & Code

    Check which failure an automated pass could expose

    A passing generated test may look reassuring even when its expected result comes from faulty code. A test checked against one repaired program may also misjudge other valid implementations, while a thread failure may stay hidden until a particular execution order occurs. Across three studies, the useful question is whether the check was placed in a position to distinguish the failure at issue. Their evidence comes from injected code faults, curated implementation panels, and controlled thread executions; each verdict stays tied to those evaluated conditions.

  3. Guided lessonSoftware & Code

    Place review where an uncertain signal would change the dataset

    A brain scan can resemble another scan without proving that both belong to one person. A math problem can resemble a benchmark question without being copied from it. In either case, acting on resemblance changes the dataset. Across identity auditing, math-data cleaning, and multilingual example construction, the useful question is where an uncertain signal meets a decision. The studies place review at different points in those workflows and measure different outcomes, so their results support a placement principle rather than one shared estimate of review’s benefit.

  11. Guided lessonSoftware & Code

    Trace software results to the behavior reached and the check applied

    A reconstructed package can pass tests, a scheduled run can expose a fault, and a patch can resolve an issue. Each result sounds like success, but the workflows reach different behavior and record different outcomes. A useful reading starts with the task supplied, follows what the method actually ran or changed, and identifies the check at the end. That path makes the studies’ claims intelligible within their tested settings.