numbas / numbas/editor

You should be able to edit part unit tests to specify behaviour that you haven't seen yet

Open
#784 0 comments 0 reactions 0 assignees View on GitHub
feature to do wishlist
Dominant language
JavaScript
Stars
60
Forks
62
PR merge metrics
No merged PRs in 30d

Description

I have a part which doesn't mark correctly at the moment. I have a list of test cases I'd like to enter, so that I can check they're all satisfied.

At the moment, the only way of creating unit tests is to save feedback you've been given in response to a submitted answer. The intention is to preserve correct marking behaviour.

But this doesn't work for test-driven design, where you write failing tests first, and then edit the question until they pass.

You should be able to create a test from scratch, or edit an existing test, specifying the values or credit awarded for certain feedback notes.

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by tracing how the editor currently creates unit tests from feedback on a submitted answer. Define the data and UI needed to create or edit tests with specified feedback values or credit, then verify that tests can be written before the marking behaviour exists and pass once the question is updated.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
testing
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.