setup season 2425 with first part of the questions
This commit is contained in:
BIN
docs/CIS_Controls_Version_8.xlsx
Normal file
BIN
docs/CIS_Controls_Version_8.xlsx
Normal file
Binary file not shown.
BIN
docs/CIS_Controls_v8_Online.22.02.pdf
Normal file
BIN
docs/CIS_Controls_v8_Online.22.02.pdf
Normal file
Binary file not shown.
15
docs/README.md
Normal file
15
docs/README.md
Normal file
@@ -0,0 +1,15 @@
|
||||
# Docs directory
|
||||
This directory contains the questions (peer week), which will dynamically be added.
|
||||
|
||||
Also in this directory you can put all kind of documentation that should be read by the professor at the end of the lab. And of course you put your answers to this directory.
|
||||
|
||||
Please use the following formats:
|
||||
|
||||
* put your answers directly into the markdown files (.md) in this directory (this can include of course any kind of code, graphics, etc.)
|
||||
* PDF files
|
||||
|
||||
# Questions
|
||||
|
||||
The questions (per week) will be added and available directly in the questionX.md files:
|
||||
|
||||
- [Questions 1](./questions-part1.md)
|
8
docs/questions-part1.md
Normal file
8
docs/questions-part1.md
Normal file
@@ -0,0 +1,8 @@
|
||||
# Questions - Part 1
|
||||
|
||||
## Unit tests - Secret keys - Linter - optimized CI/CD pipeline
|
||||
|
||||
- **Q1.1**: Provide additional unit tests to ensure that wrong input (type, values, ...) doesn't crash the application, but gets intercepted and produce a controlled error. It is possible that you have also to adjust slightly the application
|
||||
- **Q1.2**: The secret key for flask is hard coded. Is this good practice? What are the dangers? How could this be fixed?
|
||||
- **Q1.3**: Give a short description of *Linter*. Integrate a basic linter like [Flake8](https://flake8.pycqa.org/en/latest/) or [Ruff](https://github.com/astral-sh/ruff) in the existing CI/CD pipeline
|
||||
- **Q1.4 (optional)**: The run of the current CI/CD pipeline takes some time. Especially the time to setup the docker with the update and installation of all the dependencies is quite time consuming compared to the real testing time. Do you see any alternatives to speed up this process? Describe and try to implement it in your pipeline.
|
Reference in New Issue
Block a user