Enhance: Expand Receipt Search Functionality and Add Unit Tests

[artkolpakov]

Description

This pull request addresses the issue raised regarding the limited functionality of the receipt search feature in the receipt management dashboard UI (/dashboard/receipts/). The following enhancements and additions have been made to improve the receipt search functionality:

1. Expand Receipt Search Functionality

• Updated the receipt fetch search query to include additional fields such as merchant_store, purchase_category, and id.
• Conducted functional testing to confirm that the receipt search functionality has now been expanded to include searching by receipt ID, merchant/store, and category.
• Previously, the search functionality only filtered by name and date. The updated implementation provides a more comprehensive receipt search.

2. Add Comprehensive Unit Tests for Receipt Search Functionality

• Introduced two test_search_functionality unit tests in the views and api test folders' test_receipts.py files.
• These tests cover various receipt search scenarios, including exact field matches, substring matches, case insensitivity, empty queries, and nonexistent queries.
• Previously, the receipt search functionality lacked any testing coverage.

Overall, these changes aim to improve the test coverage, usability and effectiveness of the receipt search feature, providing users with more flexibility and accuracy when searching for receipts based on specific receipt attributes.

Checklist

• Ran the Black Formatter and
  djLint-er on any new code
  (checks
  will
  fail without)
• Made any changes or additions to the documentation where required
• Changes generate no new warnings/errors
• New and existing unit tests pass locally with my
  changes

What type of PR is this?

• ✨ Feature
• 🐛 Bug Fix

Added/updated tests?

• 👍 yes

Related PRs, Issues etc

• Closes bug: receipt search functionality does not support searching by receipt ID, merchant/store, and category #399

[artkolpakov]

@TreyWW it seems that the check for typos is failing because some of my substring test search queries contain partial words (e.g., "Fo" to match receipts with the "Food" purchase category). I'm unsure whether I should adjust this or if it's acceptable to overlook this check for the purpose of my unit tests. Thanks for taking your time to review the PR 🙏

[TreyWW]

Hey @artkolpakov, amazing PR by the way! You coulnadd the test files to extend-exclude = ["/bundle.js", "/bundle.js.map"] in typos.toml, and just ignore the whole test case if you want

[artkolpakov]

Hey @artkolpakov, amazing PR by the way! You coulnadd the test files to extend-exclude = ["/bundle.js", "/bundle.js.map"] in typos.toml, and just ignore the whole test case if you want

Thank you! I found a slightly cleaner solution (I simply re-adjusted the substrings in my unit tests to pass the typos check), and all the checks should be passing now.