You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Pytest was chosen because it has simple syntax and is well suited for testing Flask applications.
3
+
The CI workflow runs on push and pull requests to app_python/.
4
+
Calendar Versioning was used because this is a continuously deployed service.
5
+
6
+
## Workflow Evidence
7
+
- GitHub Actions: green successful run
8
+
- Docker Hub: image published with tags `latest` and `2026.02`
9
+
- Local tests: pytest passed successfully
10
+
11
+
## Best Practices Implemented
12
+
- Dependency caching to speed up CI runs
13
+
- Fail fast strategy: Docker build runs only after tests pass
14
+
- Secrets used for Docker Hub authentication
15
+
16
+
## Challenges
17
+
- Initial test client setup for Flask
18
+
- Fixing import paths for pytest
19
+
- Docker authentication in CI
20
+
- The issue occurred because pytest was executed using the global installation instead of the virtual environment. Running tests via python -m pytest ensured correct dependency resolution.
0 commit comments