Chiosa
Research collection

Software & Code

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

21 results

  1. Guided lessonSoftware & Code

    Match a test verdict to the failure it actually checks

    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.

  2. 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.

  10. Guided lessonSoftware & Code

    Trace each software result to the behavior its test observed

    A reconstructed package can pass tests, a proposed patch can resolve an issue, and a controlled run can trigger a bug. Each sounds like success, but each workflow reaches different behavior and records a different outcome. These studies suggest a practical reading rule: follow the route from available code or inputs to the check, then describe only the result that check observed. Their evaluations offer evidence within specific tasks, tests, and budgets, rather than a single measure of software correctness.