alexmojaki/futurecoder

Increase test coverage in the backend

Open

#137 opened on Feb 21, 2021

View on GitHub
 (2 comments) (0 reactions) (0 assignees)Python (180 forks)github user discovery
backendgood first issuehelp wanted

Repository metrics

Stars
 (1,520 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

The tests mostly cover the golden paths, i.e. users getting steps right or triggering a message step. There's lots of untested code. It can be found pretty easily by running tests with coverage. Some stuff is tested by test_frontend but that's slow and more difficult to measure coverage for so we should have pure Python tests for it. I'm particularly interested in the edge cases of bad code submissions from users, e.g:

  • Messing up an ExerciseStep in various ways, e.g. writing a solution that satisfies your own sample inputs but not the other tests.
  • Messages in steps that are returned manually, i.e. return dict(message='...') instead of a MessageStep. These tests would be specific to such steps.
  • Submissions that trigger Disallowed
  • Submissions that trigger linting errors

Contributor guide

Research direction
Run tests with coverage to find untested code, then write Python tests for edge cases such as bad submissions, manual returns, disallowed triggers, and linting errors.
Tech stack
python
Domain
backendtesting
Issue type
Test
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Pythonpytestcoverage
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65