Lab 8
Aim: List of Test Cases Used for Testing the Recruitment System
Software System
Test Cases Where the Model Passed
1. User Registration and Login
Test: A new user can successfully register with valid credentials and log in.
Result: The user receives a confirmation email and can log in with the correct
credentials.
2. Job Post Creation (Admin Feature)
Test: An admin can create a new job post with all necessary details (title, descrip-
tion, qualifications, etc.).
Result: The job post is visible to all users in the job listings.
3. Job Application Submission
Test: A user can apply for a job by submitting their resume and filling in required
details.
Result: The application is successfully saved in the database and listed under ”My
Applications.”
4. Search Functionality
Test: Users can search for jobs using keywords or filters (e.g., location, category).
Result: The search results display relevant jobs as expected.
5. Responsive Design
Test: The website is tested on different devices (mobile, tablet, desktop) for re-
sponsiveness.
Result: The website adjusts seamlessly across all screen sizes.
6. Logout Functionality
Test: A user logs out from the system after a session.
Result: The session is successfully terminated, and the user is redirected to the
login page.
7. Password Update
Test: A logged-in user updates their password.
Result: The password is updated successfully, and the user can log in with the
new credentials.
8. Admin Notifications
Test: Admin receives notifications for new job applications.
Result: Notifications appear in real-time on the admin dashboard.
9. Session Timeout
Test: The system logs out an inactive user after a set period.
Result: The user is prompted to log in again for security purposes.
1
10. Data Export (Admin Feature)
Test: The admin exports job applications to a CSV file.
Result: The file is downloaded successfully, and the data is correctly formatted.
Test Cases Where the Model Failed or Needs Improve-
ment
1. Form Validation
Test: Submitting a registration form with invalid data (e.g., missing email or weak
password).
Failure: The form allowed submission without validating certain fields, leading to
incomplete entries.
Fix Needed: Add stricter input validation for all fields, including email format,
password strength, and mandatory fields.
2. Error Handling for File Uploads
Test: A user uploads a resume in an unsupported format (e.g., ‘.exe‘).
Failure: The system crashes instead of displaying an error message.
Fix Needed: Add validation to accept only specific file types (e.g., ‘.pdf‘, ‘.docx‘)
and display an error for unsupported formats.
3. Forgot Password Feature
Test: A user requests a password reset.
Failure: The email with the reset link is not sent or is delayed significantly.
Fix Needed: Debug the email-sending functionality and optimize server-side han-
dling of such requests.
4. Admin Dashboard Performance
Test: Admin loads the dashboard with a large number of job applications.
Failure: The dashboard becomes slow or unresponsive.
Fix Needed: Optimize queries and implement pagination for large datasets.
5. Search and Filter Bugs
Test: A user applies multiple filters (e.g., location + category) in the job search.
Failure: The results do not update correctly or include irrelevant entries.
Fix Needed: Refactor the search and filtering logic to ensure consistent and ac-
curate results.
