1. Introduction

Huntd is a comprehensive job search and application tracking app designed to assist job seekers in their employment journey. This Test Plan outlines the test strategy, scope, objectives, criteria, resources, and deliverables for both the web and mobile (MVP) applications.

2. Test Strategy

2.1 Product Analysis

Purpose: To streamline the job search, application tracking, and candidate-recruiter communication.

Target Users: Job seekers and recruiters across all industries.

Functionality: Job searching, registration/login, profile creation/editing, chatting, job postings (recruiter-only), and notifications.

2.2 Test Approach

Functional Testing

GUI Testing

Exploratory Testing

2.3 Testing Scope

2.3.1 Web Application:

Registration/Login/Forgot Password

Profile Management (Candidate & Recruiter)

Job Search & Filtering

Candidate List & Chat

Job Applications

Footer & Navigation

2.3.2 Mobile Application (MVP):

Profile Access (Candidate & Recruiter)

Chats (View, Send, Archive)

Basic Settings (Notifications, Logout)

2.4 Out of Scope

Admin Panel

Performance and Security Testing

Unimplemented Mobile Features

2.5 Risks & Issues

Limited QA Resources

Delayed or unstable builds

Unclear requirements or UI discrepancies

2.6 Logistics

Testers: QA Engineers, Manual Testers

Test Period: Begins after documentation and test environments are prepared

3. Test Objectives

3.1 For Website:

Verify all core user flows including registration, login, profile editing, job search, and application.

Ensure all filters and forms function correctly.

Validate recruiter-specific features like candidate list and chat initiation.

Confirm proper display and navigation of UI components (e.g., header, footer, navigation menu).

3.2 For Mobile Application:

Validate login and registration flows, including third-party authentication.

Test chat functionality including send, view, and archive.

Check candidate/recruiter profile visibility and editing options.

Validate settings functionality: notifications, logout, and profile deactivation.

4. Test Criteria

4.1 Suspension Criteria

Suspend testing if >10% of critical tests fail or app crashes repeatedly

4.2 Exit Criteria

90% test case execution

100% pass rate for critical tests

No open critical defects

5. Resource Planning

5.1 Human Resources

QA Lead – Strategy, Supervision

Testers – Test Case Execution, Bug Reporting

5.2 System Resources

Browsers: Chrome, Firefox, Safari

Devices: Android (emulator & real), iOS (simulator or real)

Stable Internet (min. 20 Mbps)

6. Test Environment

Web testing: Latest Chrome, Firefox, Safari

Mobile testing: Android (v9+), iOS (v14+)

TestRail and Jira integration

7. Schedule & Estimation

7.1 Schedule:

Day 1: Review documentation, create test plan and RTM

Day 2: Create permission table and set up testing environments

Day 3: Write test cases for web application

Day 4: Write test cases for mobile application

Day 5: Review of written test cases, RTM linking

Day 6: Begin web application test execution

Day 7: Continue web test execution, log bugs

Day 8: Execute mobile test cases and log mobile-specific bugs

Day 9: Validate exit criteria

Day 10: Prepare and submit test summary report

7.2 Estimated Hours:

Test Plan & RTM: 5h

Test Case Writing: 8h

Execution: 8h

Bug Reporting: 5h

Test Summary: 3h

8. Test Deliverables

8.1 Before Testing:

Test Plan

RTM

Test Cases

Permission Table

8.2 During Testing:

Execution Reports

Bug Reports (Jira)

8.3 After Testing:

Final Test Report

Summary of Bugs

Huntd Test Plan