Unit Test Reports

Generated Unit Test Reports for Back-End, Front-End, and Mobile

This document summarizes the generated unit test reports for the three implementation layers of the Neighborhood Emergency Preparedness Hub project:

• Back-end
• Front-end
• Mobile

Report date: 2026-04-11

1. Back-End Unit Test Report

Technology Stack

Item	Value
Runtime	Node.js
Framework	Express.js
Test runner	Jest
Test command	npm run test:unit
Test location	backend/tests/unit

Test Execution Command

cd backend
npm run test:unit

Test Execution Result

Test Suites: 12 passed, 12 total
Tests:       211 passed, 211 total
Snapshots:   0 total
Time:        1.528 s

Result Summary

Metric	Result
Status	Passed
Test suites	12 passed / 12 total
Unit tests	211 passed / 211 total
Snapshots	0
Failed tests	0

Tested Modules

The back-end unit tests cover the main MVP modules:

Module	Tested Layers
Auth	Controller, service, validators
Profiles	Controller, service, validators
Help requests	Controller, service, validators
Availability	Controller, service, validators

Unit Test Files

backend/tests/unit/modules/auth/controller.test.js
backend/tests/unit/modules/auth/service.test.js
backend/tests/unit/modules/auth/validators.test.js
backend/tests/unit/modules/profiles/controller.test.js
backend/tests/unit/modules/profiles/service.test.js
backend/tests/unit/modules/profiles/validators.test.js
backend/tests/unit/modules/help-requests/controller.test.js
backend/tests/unit/modules/help-requests/service.test.js
backend/tests/unit/modules/help-requests/validators.test.js
backend/tests/unit/modules/availability/controller.test.js
backend/tests/unit/modules/availability/service.test.js
backend/tests/unit/modules/availability/validators.test.js

Scope of Back-End Unit Tests

The back-end unit tests verify:

• Request validation rules for all implemented modules
• Successful and failing authentication flows
• Email verification and password reset logic
• JWT-based authentication and authorization behavior
• Profile creation and update behavior
• Health, physical, location, privacy, profession, and expertise validation
• Help request creation, guest access behavior, request visibility, and status transitions
• Volunteer availability toggling, synchronization, assignment retrieval, cancellation, and resolution logic
• Controller-level error handling and expected HTTP status codes
• Service-level business logic independent from Express routing

Back-End Assessment

The back-end currently has an active and passing Jest unit test suite. The implemented module structure follows a testable layered architecture:

routes -> controller -> service -> repository -> validators

Unit tests are focused mainly on controller, service, and validator behavior. Repository/database behavior is covered separately by integration tests.

2. Front-End Unit Test Report

Technology Stack

Item	Value
Framework	Next.js
UI library	React
Language	TypeScript
Styling	CSS tokens and component-level styles
Project path	web

Current Test Configuration

The front-end project currently does not define a unit test script in web/package.json.

Current scripts:

{
  "dev": "next dev",
  "build": "next build",
  "start": "next start"
}

Test File Discovery

No project-owned front-end unit test files were found under web/src.

The only discovered test-like files are inside web/node_modules, which belong to third-party dependencies and are not part of this project's test suite.

Result Summary

Metric	Result
Status	Not configured
Test runner	Not currently installed/configured
Project-owned test files	0
Executed unit tests	0
Failed tests	Not applicable

Current Front-End Verification Approach

Although automated front-end unit tests are not yet configured, the front-end implementation is structured in a way that can support future unit testing:

• Reusable UI components are located under web/src/components/ui
• Feature-level components are located under web/src/components/feature
• Shared logic is separated under web/src/lib
• Reusable design tokens are located under web/src/styles/tokens
• Pages are implemented using the Next.js App Router under web/src/app

Recommended Future Front-End Unit Test Setup

Recommended tools:

• Vitest or Jest for unit testing
• React Testing Library for component behavior tests
• @testing-library/jest-dom for DOM assertions

Recommended initial test targets:

Area	Suggested Tests
Auth forms	Required fields, invalid email, password validation, submit behavior
Profile view/edit forms	Field rendering, validation messages, save action behavior
Shared inputs	Text input, password input, select input, textarea, verification code input
Shared buttons	Disabled, loading, click states
Utility functions	API client behavior, email validator, formatting helpers

Front-End Assessment

The front-end does not currently have generated automated unit test results. For milestone reporting, this should be recorded as a current limitation and a planned improvement. The component structure is suitable for adding unit tests in the next iteration.

3. Mobile Unit Test Report

Technology Stack

Item	Value
Platform	Android
Language	Kotlin
UI framework	Jetpack Compose
Navigation	Navigation Compose
Project path	android

Current Test Configuration

Test configuration for mobile has not been implemented in the scope of MVP. JUnit for pure Kotlin unit tests, and Compose UI testing for screen-level UI behavior are planned to be implemented.

Current Mobile Verification Approach

The mobile implementation is organized around feature screens and reusable Compose components:

Area	Examples
Auth screens	Login, signup, verify email, forgot password, reset password, complete profile
Main feature screens	Home, request help, assigned request, notifications, news, gathering areas
Profile screens	Profile, edit profile, profile data models
Shared UI components	Buttons, inputs, display cards, selection controls
Navigation	App navigation graph and route definitions

4. Overall Unit Test Status

Layer	Status	Summary
Back-end	Passing	211 unit tests passed across 12 Jest suites
Front-end	Not configured	No project-owned unit test runner or test files yet
Mobile	Not implemented yet	No unit tests yet

5. Conclusion

The back-end currently has a complete generated unit test report with all tests passing. The front-end and mobile layers do not yet have generated automated unit test results.

For the next milestone, what is planned is to add lightweight unit test setups for both front-end and mobile, focusing first on validation utilities, reusable components, and critical user flows.