Refactor user endpoint tests to include pagination and response structure validation
- Updated tests for listing users to validate pagination and response format. - Changed mock return values to include total count and pagination details. - Refactored user creation mocks for clarity and consistency. - Enhanced assertions to check for presence of pagination fields in responses. - Adjusted test cases for user retrieval and updates to ensure proper handling of user data. - Improved readability by restructuring mock definitions and assertions across various test files.
This commit is contained in:
@@ -109,9 +109,15 @@ class TestPlaylistEndpoints:
|
||||
|
||||
assert response.status_code == 200
|
||||
data = response.json()
|
||||
assert len(data) == 2
|
||||
assert "playlists" in data
|
||||
assert "total" in data
|
||||
assert "page" in data
|
||||
assert "limit" in data
|
||||
assert "total_pages" in data
|
||||
assert len(data["playlists"]) == 2
|
||||
assert data["total"] == 2
|
||||
|
||||
playlist_names = {p["name"] for p in data}
|
||||
playlist_names = {p["name"] for p in data["playlists"]}
|
||||
assert "Test Playlist" in playlist_names
|
||||
assert "Main Playlist" in playlist_names
|
||||
|
||||
|
||||
Reference in New Issue
Block a user