Skip to content

Story 19.4 - Add automated tests for feature parity #101

Description

@acbart

As an engineering team, we want automated tests so that the reimplementation preserves behavior.

Acceptance criteria:

  • Unit tests cover:

    • assignment settings serialization
    • virtual file namespace resolution
    • file visibility/editability
    • feedback category mapping
    • queued input behavior
    • part-id extraction/replacement
  • Integration tests cover:

    • run success
    • syntax error
    • runtime error
    • input program
    • instructor feedback
    • on-eval
    • on-change
    • file import/read
    • upload/download
  • End-to-end tests cover learner and instructor workflows.

  • Tests run in CI.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions