Testing Content Route API

[manojtsx]

1. POST /api/content/add/post - Add post content to the database

• On sending the title, description, blog, userId (optional), and categoryId, it shows 'Content Added Successfully' or 'Content Uploaded Successfully' message (201). You can look at the server/uploads folder for the post saved while location is saved in the db.
• If the user does not exist, it shows 'User does not exist' error (404).
• If the user role is 'viewer', it shows 'Not authorized to upload' error (401).
• If the title and description fields are empty, it shows a missing error (400).
• If the title and description fields are less than 3 characters, it shows an error indicating they must be at least 3 characters long (400).
• If the title and description fields are more than 255 characters long, it shows an error indicating they must be at most 255 characters long (400).
• If the content type is not 'pdf', 'video', or 'post', it shows 'Content Type is required' error (400).
• If the location is missing for 'pdf' or 'video' content types, it shows 'Location is required for pdf and video content type' error (400).
• If the blog is missing for 'post' content type, it shows 'Blog is required for post content type' error (400).
• If any other error occurs, it shows a server error (500).

2. . POST /api/content/add/pdf - Add pdf content to the database

• On sending the title, description, userId (optional), and categoryId, it shows 'PDF Added Successfully' or 'PDF Uploaded Successfully' message (201).
• If the user does not exist, it shows 'User does not exist' error (404).
• If the user role is 'viewer', it shows 'Not authorized to upload' error (401).
• If the title and description fields are empty, it shows a missing error (400).
• If the title and description fields are less than 3 characters, it shows an error indicating they must be at least 3 characters long (400).
• If the title and description fields are more than 255 characters long, it shows an error indicating they must be at most 255 characters long (400).
• If the content type is not 'pdf', 'video', or 'post', it shows 'Content Type is required' error (400).
• If the location is missing for 'pdf' or 'video' content types, it shows 'Location is required for pdf and video content type' error (400).
• If the blog is missing for 'post' content type, it shows 'Blog is required for post content type' error (400).
• If any other error occurs, it shows a server error (500).

3. . POST /api/content/add/video - Add video content to the database

• On sending the title, description, userId (optional), and categoryId, it shows 'Video Added Successfully' or 'Video Uploaded Successfully' message (201).
• If the user does not exist, it shows 'User does not exist' error (404).
• If the user role is 'viewer', it shows 'Not authorized to upload' error (401).
• If the title and description fields are empty, it shows a missing error (400).
• If the title and description fields are less than 3 characters, it shows an error indicating they must be at least 3 characters long (400).
• If the title and description fields are more than 255 characters long, it shows an error indicating they must be at most 255 characters long (400).
• If the content type is not 'pdf', 'video', or 'post', it shows 'Content Type is required' error (400).
• If the location is missing for 'pdf' or 'video' content types, it shows 'Location is required for pdf and video content type' error (400).
• If the blog is missing for 'post' content type, it shows 'Blog is required for post content type' error (400).
• If any other error occurs, it shows a server error (500).

4. PUT /api/content/edit/post/:id - Edit post content to the database

• On editing the title, description, blog, userId (optional), and categoryId, it shows 'Post updated successfully' message (200). Previous post will be deleted and updated post will be added to the server/uploads folder.
• If the user does not exist, it shows 'User does not exist' error (404).
• If the post does not exist, it shows 'Post does not exist' error (404).
• If the user role is 'viewer' or the user is an 'author' but not the owner of the post, it shows 'Not authorized to edit this post' error (401).
• If the title and description fields are empty, it shows a missing error (400).
• If the title and description fields are less than 3 characters, it shows an error indicating they must be at least 3 characters long (400).
• If the title and description fields are more than 255 characters long, it shows an error indicating they must be at most 255 characters long (400).
• If any other error occurs, it shows a server error (500).

5. PUT /api/content/edit/pdf/:id - Edit pdf content to the database

• On editing the title, description, userId (optional), and categoryId, it shows 'Content updated successfully' message (200). Previous pdf will be deleted and updated post will be added to the server/uploads folder.
• If the user does not exist, it shows 'User does not exist' error (404).
• If the content does not exist, it shows 'Content does not exist' error (404).
• If the user role is 'viewer' or the user is an 'author' but not the owner of the content, it shows 'Not authorized to edit this pdf' error (401).
• If the title and description fields are empty, it shows a missing error (400).
• If the title and description fields are less than 3 characters, it shows an error indicating they must be at least 3 characters long (400).
• If the title and description fields are more than 255 characters long, it shows an error indicating they must be at most 255 characters long (400).
• If any other error occurs, it shows a server error (500).

6. PUT /api/content/edit/video/:id - Edit video content to the database

• On editing the title, description, userId (optional), and categoryId, it shows 'Content updated successfully' message (200). Previous video will be deleted and updated post will be added to the server/uploads folder.
• If the user does not exist, it shows 'User does not exist' error (404).
• If the content does not exist, it shows 'Content does not exist' error (404).
• If the user role is 'viewer' or the user is an 'author' but not the owner of the content, it shows 'Not authorized to edit this video' error (401).
• If the title and description fields are empty, it shows a missing error (400).
• If the title and description fields are less than 3 characters, it shows an error indicating they must be at least 3 characters long (400).
• If the title and description fields are more than 255 characters long, it shows an error indicating they must be at most 255 characters long (400).
• If any other error occurs, it shows a server error (500).

7. DELETE /api/content/delete/:id - Delete content from the database and file from the server

• On successful deletion, it shows 'Content deleted successfully' message (200).
• If the user does not exist, it shows 'User does not exist' error (404).
• If the content does not exist, it shows 'No content to delete' error (404).
• If the user role is 'viewer' or the user is an 'author' but not the owner of the content, it shows 'Not authorized to perform this action' error (401).
• If the content location exists but cannot be deleted, it shows a server error (500).
• If any other error occurs, it shows a server error (500).

8. PUT /api/content/approve/:id - Approve content

• On successful approval, it shows 'Approved Content' message (200).
• If the user does not exist, it shows 'User does not exist' error (404).
• If the content does not exist, it shows 'Content does not exist' error (404).
• If the user role is 'viewer' or 'author', it shows 'Not authorized to perform this action' error (401).
• If the content status is already 'Uploaded', it shows 'Conflict occurred in content status' error (409).
• If any other error occurs, it shows a server error (500).

9. PUT /api/content/reject/:id - Reject cotent

• On successful rejection, it shows 'Rejected Content' message (200).
• If the user does not exist, it shows 'User does not exist' error (404).
• If the content does not exist, it shows 'Content does not exist' error (404).
• If the user role is 'viewer' or 'author', it shows 'Not authorized to perform this action' error (401).
• If the content status is already 'Rejected', it shows 'Conflict occurred in content status' error (409).
• If any other error occurs, it shows a server error (500).

10. GET /api/content/post/:id - Get post content by id

• On successful retrieval, it shows the content detail (200).
• If the content does not exist, it shows 'Content does not exist' error (404).
• If the content type is not 'post', it shows 'You are trying to open post but this is a video/pdf.' error (403).
• If any other error occurs, it shows a server error (500).

11. GET /api/content/pdf/:id - Get pdf content by id

• On successful retrieval, it shows the content detail (200).
• If the content does not exist, it shows 'Content does not exist' error (404).
• If the content type is not 'pdf', it shows 'You are trying to open pdf but this is a video/post.' error (403).
• If any other error occurs, it shows a server error (500).

12. GET /api/content/video/:id - Get video content by id

• On successful retrieval, it shows the content detail (200).
• If the content does not exist, it shows 'Content does not exist' error (404).
• If the content type is not 'video', it shows 'You are trying to open video but this is a pdf/post.' error (403).
• If any other error occurs, it shows a server error (500).

13. GET /api/content/ - Get all contents

• On successful retrieval, it shows all content details (200).
• If no content is found, it shows 'No content found' error (404).
• If a filter is provided, it filters the content by content type.
• If any other error occurs, it shows a server error (500).

14. GET /api/content/count - Get count of all contents

• If no content is found (empty array), it returns a 404 status with a message "No content found".
• It returns a 200 status with the total content count, post count, PDF count, and video count in the response.
• If an error occurs, it returns a 500 status with the error message.

Note: While calling every API, you don't forget to check the database and server/uploads folder for tracking changes.