OperationalError: no such table: missing_person in SQLite Database during Testing

[Dovineowuor]

---

Issue Title: OperationalError: no such table: missing_person in SQLite Database during Testing

Description:

During testing, the SQLite database is encountering an OperationalError indicating that the missing_person table does not exist. This error occurs when executing SQL commands that interact with this table, leading to failures in test cases.

Error Trace:

sqlite3.OperationalError: no such table: missing_person
[SQL: INSERT INTO missing_person (name, nickname, gender, x_handle_full, x_handle, status, holding_location, last_known_location, photo_url, security_organ, time_taken, time_taken_formatted, notes, released_on, age, occupation, contact_info) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)]
[parameters: ('Emily Clark', 'Em', 'Female', 'N/A', 'N/A', 'Missing', 'N/A', 'N/A', None, 'N/A', None, None, 'N/A', 'N/A', None, None, 'emily.clark@example.com')]

Test Cases Affected:

• test_create_missing_person
• test_retrieve_missing_person
• test_delete_missing_person
• test_index

Steps to Reproduce:

1. Run tests that interact with the missing_person table.
2. Observe the sqlite3.OperationalError indicating that the table does not exist.

Expected Behavior:

The missing_person table should be present in the SQLite database, allowing the tests to execute SQL commands without encountering errors.

Actual Behavior:

The missing_person table is missing, causing SQL operations to fail and resulting in test failures.

Possible Causes:

• The table may not be created in the SQLite database before the tests are run.
• Database schema might not be initialized or updated properly.
• In-memory database used for testing might not have the required tables created.

Suggested Solutions:

1. Verify that the missing_person table is correctly defined in the SQLAlchemy models.
2. Ensure that database migrations are applied, if applicable.
3. Check the test setup code to confirm that the database schema is initialized before running tests.
4. Ensure that db.create_all() is called in the test setup if using an in-memory SQLite database.
5. Review test database configuration and initialization to ensure consistency with the application schema.

---