Fix CI integration test rate limiting
- Add auth_intensive marker for tests that make many login requests - Mark all tests in test_auth_api.py with auth_intensive - Exclude auth_intensive tests from CI integration runs against deployed environments (they trigger 429 rate limiting) - Remove duplicate TestSecurityEdgeCases class definition - Register auth_intensive, integration, large, slow markers in conftest.py
This commit is contained in:
@@ -81,6 +81,8 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
|
||||
- Improved pod naming: Orchard pods now named `orchard-{env}-server-*` for clarity (#51)
|
||||
|
||||
### Fixed
|
||||
- Fixed CI integration test rate limiting: added `auth_intensive` marker and excluded auth-heavy tests from deployed environments
|
||||
- Fixed duplicate `TestSecurityEdgeCases` class definition in test_auth_api.py
|
||||
- Fixed integration tests auth: session-scoped client, configurable credentials via env vars, fail-fast on auth errors
|
||||
- Fixed Content-Disposition header encoding for non-ASCII filenames using RFC 5987 (#38)
|
||||
- Fixed deploy jobs running even when tests or security scans fail (changed rules from `when: always` to `when: on_success`) (#63)
|
||||
|
||||
Reference in New Issue
Block a user