Strategies

Classroom workflow: publish a debugging task, have students run an Evaluation session, and review the exported report and trace alongside the final solution

Strategy · All strategies
Evidence · 2 claims (2 for) · 1 study (1 design), q2 · 0 of 1 report an effect size · 2 claims rest on one study

Description

The article describes a lightweight classroom workflow: an instructor publishes a debugging task with its source, tests, and any custom test-command patterns; students open it in VS Code, run an Evaluation session, debug normally, and "submit the exported report and trace alongside their final solution". An instructor or teaching assistant then reviews the process evidence directly and can attach rubric labels through the human-label mechanism, stored as later events leaving the original trace intact.

Design Implications

Context

Requirements

Constraints

Target Learners

Target Learning Goals

Claims

Examples

-

Key Sources

Page metadata
Field Value
type strategy
id submit-debugging-trace-alongside-final-solution-workflow
title Classroom workflow: publish a debugging task, have students run an Evaluation session, and review the exported report and trace alongside the final solution
description The article describes a lightweight classroom workflow: an instructor publishes a debugging task with its source, tests, and any custom test-command patterns; students open it in VS Code, run an Evaluation session, de...
status review
generated by process:wiki-ingest on 2026-10-10
trust unverified — no one has confirmed this page's content
sources 1 — jiatong-liu-2026

Frontmatter is the page's machine-readable record — see the Schema & Guide.