MyStudyList ist ein digitaler Hausaufgabenplaner, mit dem man alle Aufgaben effizient verwalten kann. Die App richtet sich an Schüler*innen und Studierende und unterstützt dabei, das Lernen einfach und strukturiert zu planen.
- CRUD-Funktionalität – Aufgaben erstellen, anzeigen und löschen
- MongoDB-Datenbank – Speicherung aller Einträge über MongoDB Compass
- Visuelles Feedback – Aktionen wie das Löschen werden durch Bootstrap-Toasts bestätigt
- Motivations-Emojis – Aufgaben können mit Emojis versehen werden
- Suchfunktion – Aufgaben nach Datum oder Fach/Modul filtern
| Bereich | Technologie |
|---|---|
| Frontend | Angular CLI v20.0.5 |
| Backend | Node.js v22.15.1, Express.js |
| Datenbank | MongoDB Compass v6.0.24 |
| Styling | Bootstrap 5 |
The frontend is hosted with Firebase Hosting, while the backend API runs as a containerized service on Google Cloud Run. The MongoDB database remains hosted on MongoDB Atlas.
At the moment, deployment is performed manually in Google Cloud terminal:
cd MyStudyList
git pullBackend:
cd backend
gcloud run deploy mystudylist-backend \
--source . \
--region europe-west1 \
--allow-unauthenticatedFrontend:
cd frontend
npm ci
npm run build
firebase deploy --only hostingEverything is available on:
- Frontend: https://project-c5432009-c36e-4cb8-b23.web.app
- Backend: https://mystudylist-backend-612429176168.europe-west1.run.app
- Backend API: https://mystudylist-backend-612429176168.europe-west1.run.app/api/hws
Automated backend tests are implemented using Jest and Supertest.
The unit tests verify the Hw data model and its validation rules. The following cases are tested:
- valid homework entries
- missing subject (
subject) - missing date (
date) - missing task type (
task_type) - optional notes
- correct assignment of provided values
The integration tests verify the interaction between Express, the API routes, Mongoose, and an isolated MongoDB test database.
The following endpoints and scenarios are tested:
POST /api/hwsGET /api/hwsGET /api/hws/:idDELETE /api/hws/:id- error cases such as non-existing or invalid IDs
The integration tests use MongoDB Memory Server as an isolated temporary test database. This prevents test data from being written to or deleted from the production database.
The endpoint
GET /health
checks whether the backend is connected to the database.
It returns status 200 when the database is connected and status 503 when the database is unavailable.
Backend test coverage is measured using Jest Coverage.
The current backend test coverage is:
- Statements: 92.68%
- Branches: 100%
- Functions: 100%
- Lines: 92.5%
A global minimum coverage threshold of 80% is configured for statements, branches, functions, and lines. If the coverage falls below this threshold, the coverage check fails.
Run the backend tests:
npm test --prefix backend -- --runInBandRun the backend tests with coverage:
npm run test:coverage --prefix backend -- --runInBandThe backend tests and coverage check are integrated into the GitHub Actions CI pipeline.
When the CI workflow is triggered, GitHub Actions automatically installs the required dependencies and runs the backend tests including the coverage check. If a test fails or the coverage falls below the configured threshold, the backend CI job fails.
Our frontend is tested using Jasmine and Karma. We focus on isolated unit tests for components and services:
- Services: HTTP requests are intercepted and mocked using
HttpTestingController - Components: Services are mocked using spies, and a minimal router is provided for testing
Frontend Test Coverage: We currently maintain a 98% code coverage across the frontend:
- Statements: 98.36%
- Branches: 78.57%
- Lines: 98.27%
- Functions: 96.29%
There are two ways to run the frontend tests, depending on your goal:
1. Development Mode (Watch Mode)
cd frontend
npm run test2. CI Mode (Single Run & Coverage)
This is the exact command used in our GitHub Actions pipeline. It is much faster, does not open a visible browser, and generates the coverage report:
cd frontend
npx ng test --watch=false --browsers=ChromeHeadless --no-progress --code-coverageFor the end-to-end testing of the homework planner, Playwright was used. The purpose of these tests was to verify that important parts of the homework planner work correctly.
Playwright tests exist for the get, post and delete endpoints of the homework planning function. These tests send HTTP requests directly to the backend and check whether the server returns the expected status codes and data. For those test a mongoDB test database is used. The tests include:
- creating homework,
- retrieving homework entries or a specific one by id,
- handling non existing homework entry
- deleting a homework entry.
Playwright was also used to test important elements and navigation on the homepage, the planner page and the create new entry page. These tests open the deployed application in a browser and interact with it in a similar way to a real user. The tests mainly check that buttons are available and clickable, the table headings are displayed, the headings of pages show and that search fields are visible. The frontend tests are executed against the deployed version of the application.
For the API tests, Playwright is configured to automatically start the backend using: npm run start:test The test server runs locally on port 5000.
Start tests:
npx playwright testTo ensure code quality, prevent regressions, and automate our workflow, we have implemented a GitHub Actions CI pipeline. It triggers automatically on every push to main or dev, and on every Pull Request targeting main.
- Frontend Tests: Sets up Node.js, installs dependencies, runs Angular unit tests with coverage reporting, and automatically uploads the coverage report as a downloadable artifact for review.
- Backend Tests: Sets up Node.js, installs dependencies, and runs Jest tests sequentially (
--runInBand) to ensure stability and prevent Out-Of-Memory errors in the CI environment.