Initial commit

Author: github-classroom[bot]

.csse6400/bin/clean_repository.sh

@@ -0,0 +1,25 @@
+#!/bin/bash
+#
+# Ensure that students have not committed inappropriate files for a Git repository.
+
+# The following files are not allowed in a Git repository.
+ILLEGAL_FILES=(.DS_Store .localized .DS_Store? ._* .Spotlight-V100 .Trashes Thumbs.db ehthumbs.db desktop.ini)
+ILLEGAL_FILES+=(*.pyc *.pyo *.exe *.dll *.so *.a *.o *.obj *.lib)
+ILLEGAL_FILES+=(__pycache__ *.class *.jar *.war *.rar)
+
+failed=0
+for file in "${ILLEGAL_FILES[@]}"; do
+    matches=$(git ls-files "${file}" 2>/dev/null)
+    if [[ -n "${matches}" ]]; then
+        echo "Found illegal file: ${matches}"
+        failed=1
+    fi
+done
+
+if [ $failed -eq 1 ]; then
+    echo "FAIL: Found illegal files in repository."
+    echo "These files should not be committed to Git repositories - it is a good practice to add them to a .gitignore file."
+    echo "Please remove these files and try again."
+    exit 1
+fi
+

.csse6400/bin/health.sh

@@ -0,0 +1,28 @@
+#!/bin/bash
+#
+# Check that the health endpoint is returning 200
+
+# Start flask app
+poetry install --no-root
+poetry run flask --app todo run -p 6400 &
+error=$?
+pid=$!
+if [[ $error -ne 0 ]]; then
+    echo "Failed to start flask app"
+    exit 1
+fi
+
+# Wait for flask to start
+sleep 5
+
+# Check that the health endpoint is returning 200
+curl -s -o /dev/null -w "%{http_code}" http://localhost:6400/api/v1/health | grep 200
+error=$?
+if [[ $error -ne 0 ]]; then
+    echo "Failed to get 200 from health endpoint"
+    exit 1
+fi
+
+# Kill flask app
+kill $pid
+

.csse6400/bin/unittest.sh

@@ -0,0 +1,9 @@
+#!/bin/bash
+#
+# Copy the tests directory and run the tests
+
+cp -r .csse6400/tests .
+
+poetry install --no-root
+poetry run python3 -m unittest discover -s tests
+

.csse6400/bin/validate_structure.sh

@@ -0,0 +1,35 @@
+#!/bin/bash
+#
+# Validate that the repository has the following structure:
+# -- README.md
+# -- pyproject.toml
+# -- todo
+#    | -- __init__.py
+#    | -- views
+#         | -- routes.py
+
+failed=0
+for file in README.md pyproject.toml; do
+    if [ ! -f "$file" ]; then
+        echo "FAIL: Missing $file"
+        failed=1
+    fi
+done
+
+if [ ! -d todo ]; then
+    echo "FAIL: Missing todo directory"
+    failed=1
+fi
+
+for file in todo/__init__.py todo/views/routes.py; do
+    if [ ! -f "$file" ]; then
+        echo "FAIL: Missing $file"
+        failed=1
+    fi
+done
+
+if [ $failed -eq 1 ]; then
+    echo "Repository structure is not valid. Please fix the errors above."
+    exit 1
+fi
+

.csse6400/tests/test_health.py

@@ -0,0 +1,14 @@
+import unittest
+from todo import create_app
+
+class TestHealth(unittest.TestCase):
+    def setUp(self):
+        self.client = create_app().test_client()
+
+    def test_health(self):
+        response = self.client.get('/api/v1/health')
+        self.assertEqual(response.status_code, 200)
+        self.assertEqual(response.json, {'status': 'ok'})
+
+if __name__ == '__main__':
+    unittest.main()

.csse6400/tests/test_todo.py

@@ -0,0 +1,43 @@
+import unittest
+from todo import create_app
+
+TEST_TODO = {
+            "id": 1,
+            "title": "Watch CSSE6400 Lecture",
+            "description": "Watch the CSSE6400 lecture on ECHO360 for week 1",
+            "completed": True,
+            "deadline_at": "2026-02-27T18:00:00",
+            "created_at": "2026-02-20T14:00:00",
+            "updated_at": "2026-02-20T14:00:00"
+        }
+
+
+class TestTodo(unittest.TestCase):
+    def setUp(self):
+        self.client = create_app().test_client()
+
+    def test_get_todo(self):
+        response = self.client.get('/api/v1/todos')
+        self.assertEqual(response.status_code, 200)
+        self.assertEqual(response.json, [TEST_TODO])
+
+    def test_get_todo_by_id(self):
+        response = self.client.get('/api/v1/todos/1')
+        self.assertEqual(response.status_code, 200)
+        self.assertEqual(response.json, TEST_TODO)
+
+    def test_post_todo(self):
+        response = self.client.post('/api/v1/todos', json=TEST_TODO)
+        self.assertEqual(response.status_code, 201)
+        self.assertEqual(response.json, TEST_TODO)
+
+    def test_put_todo(self):
+        response = self.client.put('/api/v1/todos/1', json=TEST_TODO)
+        self.assertEqual(response.status_code, 200)
+        self.assertEqual(response.json, TEST_TODO)
+
+    def test_delete_todo(self):
+        response = self.client.delete('/api/v1/todos/1')
+        self.assertEqual(response.status_code, 200)
+        self.assertEqual(response.json, TEST_TODO)
+

.github/workflows/classroom.yml

@@ -0,0 +1,165 @@
+# Byte-compiled / optimized / DLL files
+__pycache__/
+*.py[cod]
+*$py.class
+
+# C extensions
+*.so
+
+# Distribution / packaging
+.Python
+build/
+develop-eggs/
+dist/
+downloads/
+eggs/
+.eggs/
+lib/
+lib64/
+parts/
+sdist/
+var/
+wheels/
+share/python-wheels/
+*.egg-info/
+.installed.cfg
+*.egg
+MANIFEST
+
+# PyInstaller
+#  Usually these files are written by a python script from a template
+#  before PyInstaller builds the exe, so as to inject date/other infos into it.
+*.manifest
+*.spec
+
+# Installer logs
+pip-log.txt
+pip-delete-this-directory.txt
+
+# Unit test / coverage reports
+htmlcov/
+.tox/
+.nox/
+.coverage
+.coverage.*
+.cache
+nosetests.xml
+coverage.xml
+*.cover
+*.py,cover
+.hypothesis/
+.pytest_cache/
+cover/
+
+# Translations
+*.mo
+*.pot
+
+# Django stuff:
+*.log
+local_settings.py
+db.sqlite3
+db.sqlite3-journal
+
+# Flask stuff:
+instance/
+.webassets-cache
+
+# Scrapy stuff:
+.scrapy
+
+# Sphinx documentation
+docs/_build/
+
+# PyBuilder
+.pybuilder/
+target/
+
+# Jupyter Notebook
+.ipynb_checkpoints
+
+# IPython
+profile_default/
+ipython_config.py
+
+# pyenv
+#   For a library or package, you might want to ignore these files since the code is
+#   intended to run in multiple environments; otherwise, check them in:
+# .python-version
+
+# pipenv
+#   According to pypa/pipenv#598, it is recommended to include Pipfile.lock in version control.
+#   However, in case of collaboration, if having platform-specific dependencies or dependencies
+#   having no cross-platform support, pipenv may install dependencies that don't work, or not
+#   install all needed dependencies.
+#Pipfile.lock
+
+# poetry
+#   Similar to Pipfile.lock, it is generally recommended to include poetry.lock in version control.
+#   This is especially recommended for binary packages to ensure reproducibility, and is more
+#   commonly ignored for libraries.
+#   https://python-poetry.org/docs/basic-usage/#commit-your-poetrylock-file-to-version-control
+poetry.lock
+
+# pdm
+#   Similar to Pipfile.lock, it is generally recommended to include pdm.lock in version control.
+#pdm.lock
+#   pdm stores project-wide configurations in .pdm.toml, but it is recommended to not include it
+#   in version control.
+#   https://pdm.fming.dev/#use-with-ide
+.pdm.toml
+
+# PEP 582; used by e.g. github.com/David-OConnor/pyflow and github.com/pdm-project/pdm
+__pypackages__/
+
+# Celery stuff
+celerybeat-schedule
+celerybeat.pid
+
+# SageMath parsed files
+*.sage.py
+
+# Environments
+.env
+.venv
+env/
+venv/
+ENV/
+env.bak/
+venv.bak/
+
+# Spyder project settings
+.spyderproject
+.spyproject
+
+# Rope project settings
+.ropeproject
+
+# mkdocs documentation
+/site
+
+# mypy
+.mypy_cache/
+.dmypy.json
+dmypy.json
+
+# Pyre type checker
+.pyre/
+
+# pytype static type analyzer
+.pytype/
+
+# Cython debug symbols
+cython_debug/
+
+# PyCharm
+#  JetBrains specific template is maintained in a separate JetBrains.gitignore that can
+#  be found at https://github.com/github/gitignore/blob/main/Global/JetBrains.gitignore
+#  and can be added to the global gitignore or merged into this file.  For a more nuclear
+#  option (not recommended) you can uncomment the following to ignore the entire idea folder.
+.idea/
+*.iml
+
+# Ignore Apple junk files.
+**/.DS_Store
+**/._.DS_Store

.gitignore

@@ -0,0 +1,12 @@
+# CSSE6400 Week 1 Practical
+
+Construction of a simple HTTP server in Python.
+
+Please see the [instructions](https://csse6400.uqcloud.net/practicals/week01.pdf) for more details.
+
+Update this README file with appropriate information about your project,
+including how to run it.
+
+There are [resources](https://www.makeareadme.com) available to help you write a good README file.
+
+