MIF_E31221222/sigap-website/BLACKBOX_TEST_SCENARIOS.md

BLACKBOX TEST SCENARIOS - SIGAP JEMBER

Test Case Overview

Test Case Id	Fitur	Test Scenario	Test Step	Expected Result
TCA001	Signin	User Authentication	Multiple steps	User successfully logs in
TCA002	Forgot Password	Password Recovery	Multiple steps	Password reset successful
TCA003	Dashboard	Dashboard Access	Multiple steps	Dashboard loads correctly
TCA004	Map	Interactive Map	Multiple steps	Map displays and functions properly
TCA005	Crime Overview	Crime Statistics	Multiple steps	Statistics display correctly
TCA006	Management Incident Logs	Incident Log CRUD	Multiple steps	CRUD operations work
TCA007	Management Crime Incidents	Crime Incident CRUD	Multiple steps	CRUD operations work
TCA008	Management Crime Summary	Crime Summary Reports	Multiple steps	Reports generate correctly
TCA009	Management Users	User Management	Multiple steps	User CRUD operations work
TCA010	Management Task	Task Management	Multiple steps	Task CRUD operations work
TCA011	Management Districts	District Management	Multiple steps	District CRUD operations work
TCA012	Management Geographies	Geographic Management	Multiple steps	Geography CRUD operations work
TCA013	Management Units	Unit Management	Multiple steps	Unit CRUD operations work
TCA014	Management Coordinates/locations	Location Management	Multiple steps	Location CRUD operations work
TCA015	Management Demographies	Demographics Management	Multiple steps	Demographics CRUD operations work

---

DETAILED TEST SCENARIOS

TCA001 - SIGN IN

Test Scenario 1: Valid User Login

Objective: Verify that users with valid credentials can successfully log in

Test Steps:

1. Navigate to the sign-in page (/auth/sign-in)
2. Enter a valid email address in the email field
3. Enter a valid password (minimum 6 characters) in the password field
4. Click the "Sign In" button
5. Wait for authentication process

Expected Results:

• Form validation passes
• Loading state shows "Signing in..."
• User is redirected to dashboard (/dashboard)
• No error messages displayed

Test Scenario 2: Invalid Email Format

Objective: Verify form validation for invalid email format

Test Steps:

1. Navigate to the sign-in page
2. Enter an invalid email format (e.g., "invalid-email")
3. Enter a valid password
4. Click "Sign In" or move focus away from email field

Expected Results:

• Error message: "Enter a valid email address"
• Form submission is prevented
• Email field shows red border

Test Scenario 3: Password Too Short

Objective: Verify password length validation

Test Steps:

1. Navigate to the sign-in page
2. Enter a valid email address
3. Enter a password with less than 6 characters
4. Click "Sign In" or move focus away from password field

Expected Results:

• Error message: "Password must be at least 6 characters"
• Form submission is prevented
• Password field shows red border

Test Scenario 4: Invalid Credentials

Objective: Verify error handling for invalid credentials

Test Steps:

1. Navigate to the sign-in page
2. Enter a valid email format but non-existent email
3. Enter a password
4. Click "Sign In"

Expected Results:

• Error toast notification appears
• Error message: "Sign in failed" or specific error from server
• User remains on sign-in page
• Form fields are cleared or retain values

Test Scenario 5: Empty Form Submission

Objective: Verify form validation for empty fields

Test Steps:

1. Navigate to the sign-in page
2. Leave email field empty
3. Leave password field empty
4. Click "Sign In"

Expected Results:

• Validation errors appear for both fields
• Form submission is prevented
• Error messages indicate required fields

Test Scenario 6: Loading State

Objective: Verify loading state during authentication

Test Steps:

1. Navigate to the sign-in page
2. Enter valid credentials
3. Click "Sign In"
4. Observe button state during authentication

Expected Results:

• Button text changes to "Signing in..."
• Button becomes disabled
• Form fields become disabled
• Loading state persists until authentication completes

---

TCA002 - FORGOT PASSWORD

Test Scenario 1: Valid Email Password Reset Request

Objective: Verify password reset email can be sent to valid email

Test Steps:

1. Navigate to forgot password page (/auth/forgot-password)
2. Enter a valid registered email address
3. Click submit or press Enter
4. Wait for email sending process

Expected Results:

• Loading toast: "Sending reset email..."
• Success toast: "Password reset email sent!"
• Form switches to reset code input mode
• Email field becomes hidden

Test Scenario 2: Invalid Email Format

Objective: Verify email format validation

Test Steps:

1. Navigate to forgot password page
2. Enter invalid email format (e.g., "invalid-email")
3. Click submit

Expected Results:

• Error message: "Enter a valid email address"
• Form submission is prevented
• Email field shows red border

Test Scenario 3: Non-existent Email

Objective: Verify error handling for non-existent email

Test Steps:

1. Navigate to forgot password page
2. Enter valid email format but non-existent email
3. Click submit

Expected Results:

• Error toast notification appears
• Error message from server about email not found
• User remains on same form state

Test Scenario 4: Password Reset with Valid Code

Objective: Verify password can be reset with valid code

Test Steps:

1. Complete email submission successfully
2. Enter the reset code received via email
3. Enter new password (minimum 6 characters)
4. Click submit

Expected Results:

• Loading toast: "Resetting password..."
• Success toast: "Password reset successful!"
• User is redirected to sign-in page
• New password is active

Test Scenario 5: Invalid Reset Code

Objective: Verify error handling for invalid reset code

Test Steps:

1. Complete email submission successfully
2. Enter invalid reset code
3. Enter new password
4. Click submit

Expected Results:

• Error toast notification appears
• Error message about invalid code
• Form retains entered values
• User can retry with correct code

Test Scenario 6: Password Too Short in Reset

Objective: Verify password validation during reset

Test Steps:

1. Complete email submission successfully
2. Enter valid reset code
3. Enter password with less than 6 characters
4. Click submit

Expected Results:

• Error message: "Password must be at least 6 characters"
• Form submission is prevented
• Password field shows red border

---

TCA003 - DASHBOARD

Test Scenario 1: Authenticated User Dashboard Access

Objective: Verify authenticated users can access dashboard

Test Steps:

1. Sign in with valid credentials
2. Navigate to dashboard (/dashboard)
3. Observe dashboard layout and components

Expected Results:

• Dashboard loads successfully
• All dashboard components are visible
• Navigation sidebar is present
• User information is displayed correctly

Test Scenario 2: Unauthenticated User Dashboard Access

Objective: Verify unauthenticated users are redirected

Test Steps:

1. Clear browser session/cookies
2. Navigate directly to dashboard URL
3. Observe redirect behavior

Expected Results:

• User is automatically redirected to sign-in page
• Dashboard is not accessible
• No dashboard content is displayed

Test Scenario 3: Dashboard Navigation

Objective: Verify dashboard navigation works correctly

Test Steps:

1. Access dashboard as authenticated user
2. Click on different navigation menu items
3. Verify page transitions

Expected Results:

• Navigation between sections works smoothly
• URL updates correctly
• Page content loads without errors
• Active menu item is highlighted

Test Scenario 4: Dashboard Responsive Design

Objective: Verify dashboard works on different screen sizes

Test Steps:

1. Access dashboard on desktop
2. Resize browser window to mobile size
3. Test navigation and layout

Expected Results:

• Dashboard adapts to screen size
• Mobile navigation works correctly
• All components remain functional
• No horizontal scrolling issues

---

TCA004 - MAP

Test Scenario 1: Interactive Map Loading

Objective: Verify map loads and displays correctly

Test Steps:

1. Navigate to map section (/dashboard/map)
2. Wait for map to load
3. Observe map components

Expected Results:

• Map loads without errors
• Map tiles are visible
• Zoom controls are functional
• Map is interactive

Test Scenario 2: Map Navigation Controls

Objective: Verify map navigation controls work

Test Steps:

1. Access map page
2. Use zoom in/out controls
3. Pan the map in different directions
4. Use fullscreen toggle

Expected Results:

• Zoom controls respond correctly
• Map pans smoothly
• Fullscreen mode works
• Map state is maintained

Test Scenario 3: Crime Location Markers

Objective: Verify crime incident markers display on map

Test Steps:

1. Access map with crime data
2. Look for location markers
3. Click on markers to view details

Expected Results:

• Crime markers are visible on map
• Markers are positioned correctly
• Clicking markers shows incident details
• Different crime types have different markers

Test Scenario 4: Map Filtering

Objective: Verify map filtering functionality

Test Steps:

1. Access map page
2. Use filter controls (date range, crime type, etc.)
3. Observe map updates

Expected Results:

• Filters apply correctly
• Map updates to show filtered data
• Markers update based on filters
• Filter state is maintained

Test Scenario 5: Map Performance

Objective: Verify map performs well with large datasets

Test Steps:

1. Load map with many crime incidents
2. Navigate and zoom around map
3. Apply various filters

Expected Results:

• Map loads within reasonable time
• Navigation is smooth
• No performance degradation
• Memory usage is stable

---

TCA005 - CRIME OVERVIEW

Test Scenario 1: Crime Statistics Display

Objective: Verify crime statistics are displayed correctly

Test Steps:

1. Navigate to crime overview section
2. Observe various charts and statistics
3. Check data accuracy

Expected Results:

• All charts load correctly
• Statistics are accurate
• Data is up-to-date
• Charts are interactive

Test Scenario 2: Chart Interactions

Objective: Verify chart interactivity works

Test Steps:

1. Access crime overview page
2. Hover over chart elements
3. Click on chart sections
4. Use chart controls

Expected Results:

• Hover effects show data details
• Click interactions work
• Chart controls are functional
• Data filtering works

Test Scenario 3: Time-based Filtering

Objective: Verify time-based data filtering

Test Steps:

1. Access crime overview
2. Change date range filters
3. Observe chart updates

Expected Results:

• Date filters work correctly
• Charts update with new data
• Data consistency is maintained
• Loading states are shown

Test Scenario 4: Export Functionality

Objective: Verify data export features

Test Steps:

1. Access crime overview
2. Look for export options
3. Attempt to export data

Expected Results:

• Export options are available
• Export formats are supported
• Downloads work correctly
• Data integrity is maintained

---

TCA006 - MANAGEMENT INCIDENT LOGS

Test Scenario 1: Incident Logs List View

Objective: Verify incident logs are displayed in table format

Test Steps:

1. Navigate to incident logs management
2. Observe the logs table
3. Check pagination and sorting

Expected Results:

• Incident logs are displayed in table
• Pagination works correctly
• Sorting by columns works
• Search functionality works

Test Scenario 2: Create New Incident Log

Objective: Verify new incident log can be created

Test Steps:

1. Access incident logs management
2. Click "Add New" or "Create" button
3. Fill in required fields
4. Submit the form

Expected Results:

• Form opens correctly
• Required field validation works
• Form submission is successful
• New log appears in table

Test Scenario 3: Edit Incident Log

Objective: Verify existing incident log can be edited

Test Steps:

1. Access incident logs table
2. Click edit button on a log entry
3. Modify some fields
4. Save changes

Expected Results:

• Edit form opens with current data
• Changes are saved successfully
• Updated data appears in table
• No data loss occurs

Test Scenario 4: Delete Incident Log

Objective: Verify incident log can be deleted

Test Steps:

1. Access incident logs table
2. Click delete button on a log entry
3. Confirm deletion
4. Verify removal

Expected Results:

• Confirmation dialog appears
• Deletion is successful
• Log is removed from table
• No orphaned data remains

Test Scenario 5: Incident Log Details View

Objective: Verify detailed view of incident log

Test Steps:

1. Access incident logs table
2. Click on a log entry to view details
3. Observe detailed information

Expected Results:

• Detailed view opens correctly
• All log information is displayed
• Related data is shown
• Navigation back to list works

---

TCA007 - MANAGEMENT CRIME INCIDENTS

Test Scenario 1: Crime Incidents List View

Objective: Verify crime incidents are displayed correctly

Test Steps:

1. Navigate to crime incidents management
2. Observe the incidents table
3. Check filtering and search

Expected Results:

• Incidents are displayed in table
• Filtering works correctly
• Search functionality works
• Pagination is functional

Test Scenario 2: Create New Crime Incident

Objective: Verify new crime incident can be created

Test Steps:

1. Access crime incidents management
2. Click "Add New Incident"
3. Fill in incident details
4. Submit the form

Expected Results:

• Form opens with all required fields
• Validation works correctly
• Submission is successful
• New incident appears in list

Test Scenario 3: Edit Crime Incident

Objective: Verify crime incident can be edited

Test Steps:

1. Access crime incidents table
2. Click edit on an incident
3. Modify incident details
4. Save changes

Expected Results:

• Edit form loads with current data
• Changes are saved successfully
• Updated incident appears in table
• Data integrity is maintained

Test Scenario 4: Delete Crime Incident

Objective: Verify crime incident can be deleted

Test Steps:

1. Access crime incidents table
2. Click delete on an incident
3. Confirm deletion
4. Verify removal

Expected Results:

• Confirmation dialog appears
• Deletion is successful
• Incident is removed from table
• Related data is handled properly

Test Scenario 5: Crime Incident Details

Objective: Verify detailed view of crime incident

Test Steps:

1. Access crime incidents table
2. Click on incident to view details
3. Observe comprehensive information

Expected Results:

• Detailed view shows all incident data
• Related evidence is displayed
• Witness information is shown
• Timeline is accurate

---

TCA008 - MANAGEMENT CRIME SUMMARY

Test Scenario 1: Crime Summary Reports

Objective: Verify crime summary reports are generated correctly

Test Steps:

1. Navigate to crime summary section
2. Generate various summary reports
3. Check report accuracy

Expected Results:

• Reports generate successfully
• Data is accurate and current
• Different report types work
• Export functionality works

Test Scenario 2: Summary Report Filtering

Objective: Verify report filtering works correctly

Test Steps:

1. Access crime summary reports
2. Apply different filters (date, location, type)
3. Generate filtered reports

Expected Results:

• Filters apply correctly
• Reports update based on filters
• Data consistency is maintained
• Performance is acceptable

Test Scenario 3: Report Export

Objective: Verify reports can be exported

Test Steps:

1. Generate a crime summary report
2. Click export button
3. Choose export format
4. Download report

Expected Results:

• Export options are available
• Downloads work correctly
• File formats are supported
• Data integrity is maintained

---

TCA009 - MANAGEMENT USERS

Test Scenario 1: Users List View

Objective: Verify users are displayed in management table

Test Steps:

1. Navigate to users management
2. Observe users table
3. Check search and filtering

Expected Results:

• Users are displayed in table
• Search functionality works
• Filtering works correctly
• Pagination is functional

Test Scenario 2: Create New User

Objective: Verify new user can be created

Test Steps:

1. Access users management
2. Click "Add New User"
3. Fill in user details
4. Submit form

Expected Results:

• Form opens with required fields
• Validation works correctly
• User is created successfully
• New user appears in table

Test Scenario 3: Edit User

Objective: Verify user details can be edited

Test Steps:

1. Access users table
2. Click edit on a user
3. Modify user information
4. Save changes

Expected Results:

• Edit form loads with current data
• Changes are saved successfully
• Updated user appears in table
• Permissions are maintained

Test Scenario 4: Delete User

Objective: Verify user can be deleted

Test Steps:

1. Access users table
2. Click delete on a user
3. Confirm deletion
4. Verify removal

Expected Results:

• Confirmation dialog appears
• Deletion is successful
• User is removed from table
• Related data is handled

Test Scenario 5: User Role Management

Objective: Verify user roles can be managed

Test Steps:

1. Access user management
2. Edit user roles
3. Assign different permissions
4. Save changes

Expected Results:

• Role assignment works correctly
• Permissions are applied
• Changes are saved
• Access control works

---

TCA010 - MANAGEMENT TASK

Test Scenario 1: Task List View

Objective: Verify tasks are displayed correctly

Test Steps:

1. Navigate to task management
2. Observe tasks table/kanban board
3. Check task status and priority

Expected Results:

• Tasks are displayed correctly
• Status indicators work
• Priority levels are shown
• Filtering works

Test Scenario 2: Create New Task

Objective: Verify new task can be created

Test Steps:

1. Access task management
2. Click "Add New Task"
3. Fill in task details
4. Assign to user/team
5. Submit form

Expected Results:

• Form opens with required fields
• Assignment options work
• Task is created successfully
• New task appears in list

Test Scenario 3: Update Task Status

Objective: Verify task status can be updated

Test Steps:

1. Access task management
2. Select a task
3. Change task status
4. Save changes

Expected Results:

• Status change is successful
• Task moves to correct status column
• Updates are reflected immediately
• History is maintained

Test Scenario 4: Delete Task

Objective: Verify task can be deleted

Test Steps:

1. Access task management
2. Select a task to delete
3. Confirm deletion
4. Verify removal

Expected Results:

• Confirmation dialog appears
• Deletion is successful
• Task is removed from list
• No orphaned references

---

TCA011 - MANAGEMENT DISTRICTS

Test Scenario 1: Districts List View

Objective: Verify districts are displayed correctly

Test Steps:

1. Navigate to districts management
2. Observe districts table
3. Check district information

Expected Results:

• Districts are displayed in table
• District details are accurate
• Search functionality works
• Pagination works

Test Scenario 2: Create New District

Objective: Verify new district can be created

Test Steps:

1. Access districts management
2. Click "Add New District"
3. Fill in district details
4. Submit form

Expected Results:

• Form opens with required fields
• Validation works correctly
• District is created successfully
• New district appears in table

Test Scenario 3: Edit District

Objective: Verify district can be edited

Test Steps:

1. Access districts table
2. Click edit on a district
3. Modify district information
4. Save changes

Expected Results:

• Edit form loads with current data
• Changes are saved successfully
• Updated district appears in table
• Data integrity is maintained

Test Scenario 4: Delete District

Objective: Verify district can be deleted

Test Steps:

1. Access districts table
2. Click delete on a district
3. Confirm deletion
4. Verify removal

Expected Results:

• Confirmation dialog appears
• Deletion is successful
• District is removed from table
• Related data is handled properly

---

TCA012 - MANAGEMENT GEOGRAPHIES

Test Scenario 1: Geographies List View

Objective: Verify geographic data is displayed correctly

Test Steps:

1. Navigate to geographies management
2. Observe geographic data table
3. Check geographic information

Expected Results:

• Geographic data is displayed correctly
• Coordinates are accurate
• Search functionality works
• Data is well-organized

Test Scenario 2: Create New Geographic Entry

Objective: Verify new geographic data can be added

Test Steps:

1. Access geographies management
2. Click "Add New"
3. Fill in geographic details
4. Submit form

Expected Results:

• Form opens with required fields
• Coordinate validation works
• Entry is created successfully
• New entry appears in table

Test Scenario 3: Edit Geographic Data

Objective: Verify geographic data can be edited

Test Steps:

1. Access geographies table
2. Click edit on an entry
3. Modify geographic information
4. Save changes

Expected Results:

• Edit form loads with current data
• Changes are saved successfully
• Updated data appears in table
• Coordinate accuracy is maintained

Test Scenario 4: Delete Geographic Entry

Objective: Verify geographic entry can be deleted

Test Steps:

1. Access geographies table
2. Click delete on an entry
3. Confirm deletion
4. Verify removal

Expected Results:

• Confirmation dialog appears
• Deletion is successful
• Entry is removed from table
• No orphaned references remain

---

TCA013 - MANAGEMENT UNITS

Test Scenario 1: Units List View

Objective: Verify units are displayed correctly

Test Steps:

1. Navigate to units management
2. Observe units table
3. Check unit information

Expected Results:

• Units are displayed in table
• Unit details are accurate
• Search functionality works
• Pagination works

Test Scenario 2: Create New Unit

Objective: Verify new unit can be created

Test Steps:

1. Access units management
2. Click "Add New Unit"
3. Fill in unit details
4. Submit form

Expected Results:

• Form opens with required fields
• Validation works correctly
• Unit is created successfully
• New unit appears in table

Test Scenario 3: Edit Unit

Objective: Verify unit can be edited

Test Steps:

1. Access units table
2. Click edit on a unit
3. Modify unit information
4. Save changes

Expected Results:

• Edit form loads with current data
• Changes are saved successfully
• Updated unit appears in table
• Data integrity is maintained

Test Scenario 4: Delete Unit

Objective: Verify unit can be deleted

Test Steps:

1. Access units table
2. Click delete on a unit
3. Confirm deletion
4. Verify removal

Expected Results:

• Confirmation dialog appears
• Deletion is successful
• Unit is removed from table
• Related assignments are handled

---

TCA014 - MANAGEMENT COORDINATES/LOCATIONS

Test Scenario 1: Locations List View

Objective: Verify locations are displayed correctly

Test Steps:

1. Navigate to locations management
2. Observe locations table
3. Check location coordinates

Expected Results:

• Locations are displayed in table
• Coordinates are accurate
• Search functionality works
• Map integration works

Test Scenario 2: Create New Location

Objective: Verify new location can be created

Test Steps:

1. Access locations management
2. Click "Add New Location"
3. Fill in location details and coordinates
4. Submit form

Expected Results:

• Form opens with required fields
• Coordinate validation works
• Location is created successfully
• New location appears in table

Test Scenario 3: Edit Location

Objective: Verify location can be edited

Test Steps:

1. Access locations table
2. Click edit on a location
3. Modify location information
4. Save changes

Expected Results:

• Edit form loads with current data
• Changes are saved successfully
• Updated location appears in table
• Coordinate accuracy is maintained

Test Scenario 4: Delete Location

Objective: Verify location can be deleted

Test Steps:

1. Access locations table
2. Click delete on a location
3. Confirm deletion
4. Verify removal

Expected Results:

• Confirmation dialog appears
• Deletion is successful
• Location is removed from table
• Related incidents are handled properly

Test Scenario 5: Location Map Integration

Objective: Verify location data integrates with map

Test Steps:

1. Access locations management
2. View location on map
3. Verify coordinate accuracy
4. Test map interactions

Expected Results:

• Locations appear correctly on map
• Coordinates are accurate
• Map interactions work
• Data synchronization is maintained

---

TCA015 - MANAGEMENT DEMOGRAPHICS

Test Scenario 1: Demographics List View

Objective: Verify demographics data is displayed correctly

Test Steps:

1. Navigate to demographics management
2. Observe demographics table
3. Check demographic information

Expected Results:

• Demographics are displayed in table
• Data is accurate and current
• Search functionality works
• Statistics are calculated correctly

Test Scenario 2: Create New Demographics Entry

Objective: Verify new demographics data can be added

Test Steps:

1. Access demographics management
2. Click "Add New"
3. Fill in demographic details
4. Submit form

Expected Results:

• Form opens with required fields
• Validation works correctly
• Entry is created successfully
• New entry appears in table

Test Scenario 3: Edit Demographics

Objective: Verify demographics can be edited

Test Steps:

1. Access demographics table
2. Click edit on an entry
3. Modify demographic information
4. Save changes

Expected Results:

• Edit form loads with current data
• Changes are saved successfully
• Updated data appears in table
• Statistics are recalculated

Test Scenario 4: Delete Demographics Entry

Objective: Verify demographics entry can be deleted

Test Steps:

1. Access demographics table
2. Click delete on an entry
3. Confirm deletion
4. Verify removal

Expected Results:

• Confirmation dialog appears
• Deletion is successful
• Entry is removed from table
• Statistics are updated accordingly

Test Scenario 5: Demographics Reports

Objective: Verify demographics reports are generated

Test Steps:

1. Access demographics management
2. Generate demographic reports
3. Check report accuracy
4. Test export functionality

Expected Results:

• Reports generate successfully
• Data is accurate
• Export functionality works
• Charts and graphs display correctly

---

TEST EXECUTION NOTES

Prerequisites

• Test environment is properly configured
• Test data is available
• User accounts with appropriate permissions are set up
• Browser compatibility is verified

Test Data Requirements

• Valid user accounts for authentication testing
• Sample crime incident data
• Geographic coordinate data
• Demographic statistics
• User management test accounts

Browser Compatibility

• Chrome (latest version)
• Firefox (latest version)
• Safari (latest version)
• Edge (latest version)

Performance Criteria

• Page load time < 3 seconds
• Form submission response < 2 seconds
• Map interactions < 1 second
• Database operations < 5 seconds

Security Considerations

• Authentication tokens are properly handled
• Session management works correctly
• Input validation prevents injection attacks
• Authorization controls are enforced

Accessibility Testing

• Keyboard navigation works
• Screen reader compatibility
• Color contrast meets WCAG standards
• Form labels are properly associated

---

DEFECT REPORTING

When defects are found during testing, include the following information:

1. Test Case ID: Reference the specific test case
2. Test Scenario: Description of the scenario being tested
3. Steps to Reproduce: Detailed steps to reproduce the issue
4. Expected Result: What should happen
5. Actual Result: What actually happened
6. Environment: Browser, OS, version information
7. Severity: Critical, High, Medium, Low
8. Priority: P1, P2, P3, P4
9. Screenshots: Visual evidence of the issue
10. Additional Notes: Any other relevant information