Backend Memo

[aldy505]

I'm not the project lead, so...

Regarding data

• Schema for the InfluxDB (how many tables do we need, agreement for the schema of each tables) #34
• Input validation for events (mouse, keyboard, and webcam input), regular data (identity & SAM assessment) #37

Regarding events

• Route for sending events #99
• Logic for inserting the event into the database #100
• Logic to do things post-event. We should compile and generate some data:
  • Word per minute
  • Deletion rate (how many times the user pressed backspace or delete within a minute)
  • Fun-facts about the tests

Regarding the identity

• Route for submitting user data #101
• Route for submitting SAM assessment #102

Regarding session

• Route for providing JWT token for client #103

Regarding coding test

• Route for code test & submission (interact with Piston API) #104
• Backend: implement Piston domain #131
• Storing code data (current code, language, scratchpad) into InfluxDB #105
• Setup unit test to be run for the given code submission
  • Code submission unit test: C #106
  • Code submission unit test: C++ #107
  • Code submission unit test: PHP #108
  • Code submission unit test: Javascript #109
  • Code submission unit test: Java #110
  • Code submission unit test: Python #111

Regarding forwarded routes

• Forwarding frontend error logs into backend #112

Fetching the results

• Logic to convert each user's data into a CSV or JSON file, then store it to the S3 bucket, put the link into the InfluxDB (moved to Worker app to render data #50)
• Route for getting the links of the CSV or JSON files (moved to Worker app to render data #50)
• Documentation for worker service #157

Others

• Backend integration test #130
• Backend: Implement question repository #132
• Bikin contoh penggunaan SignalR client #133
• Test backend domain models #128
• Test DomainObjectMapper #129
• Documentation for logger service #154
• Documentation for dummy directory #155
• Documentation for proto directory (including the commands) #156

If there's anything else to add, let me know by commenting it below.

cc @ronnygunawan @RayWP @vmasdani

[aldy505]

Buat assertion question test nya, kecuali yang twinkle twinkle little star (karena itu butuh assertion di level application), dibikin formatnya gini:

Misalnya ada 5 test cases:

#1 - Passing
#2 - Passing
#3 - Passing
#4 - Passing
#5 - Failed (expected: [something], got: [something])

RFC

[aldy505]

Alternatif format kedua:

#1
PASSING
#2
PASSING
#3
PASSING
#4
PASSING
#5
FAILED
EXPECTED [something]
GOT [something]

[ronnygunawan]

Markdown style:

# 1 PASSING
# 2 PASSING
# 3 PASSING
# 4 PASSING
# 5 FAILED
> EXPECTED [something]
> GOT [something]