Skip to content

CTF-120: Challenge Ratings

Statement

The system could support participant ratings of challenges. Participants who have solved a challenge could rate it on a numeric scale. The system shall display the average rating and rating count per challenge. Rating visibility shall be configurable per event (public, organizer-only, or disabled).

Rationale

Ratings help organizers identify well-received vs frustrating challenges and improve challenge design over time, especially when challenge libraries are reused across events. Participant feedback on challenge quality is valuable for iterating on content. (CTFd supports a similar challenge rating feature.)

Traceability

  • IMPLEMENTS → CODE_FILE shifter/shifter_platform/ctf/models/ (CTFChallengeRating model and rating_visibility on CTFEvent)
  • IMPLEMENTS → CODE_FILE shifter/shifter_platform/ctf/services/submission.py (rate_challenge() and get_challenge_rating() service functions)
  • IMPLEMENTS → CODE_FILE shifter/shifter_platform/ctf/enums.py (RatingVisibility enum (PUBLIC, ORGANIZER, DISABLED))
  • IMPLEMENTS → CODE_FILE shifter/shifter_platform/ctf/urls.py (api_rate_challenge URL route)
  • IMPLEMENTS → CODE_FILE shifter/shifter_platform/ctf/migrations/0016_add_challenge_ratings.py (Migration adding CTFChallengeRating table and rating_visibility field)
  • IMPLEMENTS → CODE_FILE shifter/shifter_platform/ctf/forms/ (rating_visibility field in event admin form)
  • IMPLEMENTS → CODE_FILE shifter/shifter_platform/ctf/services/event/ (Event service with rating_visibility handling)
  • IMPLEMENTS → GITHUB_ISSUE Brad-Edwards/bigrae#554 (CTF-120: Challenge Ratings)