To improve the quality of our end-to-end testing code, we want to create lint checks for common bad practices. If you would like to help with this issue, please leave a comment on this issue with the task you want to work on.

How to Write E2E Lint Checks

1. First think about how you can identify the bad practice based solely on the text of the code. Imagine you get a code file as a string

When a user has a version of gradebook.db that has not been upgraded to the latest version,
Formgrader will hang when it tries to open the database file.
The error is only visible in the log output and not propagated to the web interface.

There is an Autolab dark theme PR which allows each individual user to set whether they want the default Autolab theme, or the dark theme: autolab/Autolab#1139

This is a very promising PR but there are some issues with it which needs to be resolved before it can be merged.

1. Certain aspects of the light theme (the handin-panel, the font colors and type, the handin ta

git-cz serves the purpose here.