---
# System prepended metadata

title: Autograder design thoughts (group 1)
tags: [ccss-summer-dev-projects]

---

# Autograder design thoughts (group 1)

###### tags: `ccss-summer-dev-projects`

## When a student uses the platform, what should it look like?
- Simple design, allow student to paste their 'key'?
- Upload source code to test

### To consider
- Maybe a VSCode extension to directly submit instead of having to zip

## When a prof uses the platform, what should it look like?
- Table to visualize/manage students in class
- Admin tools, eg. see class progress, individual submissions, statistics
- Upload tests for different questions/have a bank of tests?
- 

### To consider
- What does creating a new assignment look like?
- What does creating new tests looks like?
- What level of customization do professors have over the results sent to student?


## When a student submits an assignment, what considerations should there be?
- Dynamically display results
- Results page should have some info about what went wrong (detailed error messages)

### To consider
- How will professor create and submit the tests to be ran?
- 