Skip to content

Conversation

@eesa456
Copy link
Contributor

@eesa456 eesa456 commented May 22, 2025

No description provided.

@github-actions
Copy link

💥 Something went wrong while deploying the pull request environment.
Check Output Logs

@github-actions
Copy link

🚀 PR environment successfully deployed.
Commit Hash: 4ac28a35d97172c28c63a164bf37db34cf908b5d
URL: https://nrl1205-3a0f35.api.record-locator.dev.national.nhs.uk/


event = create_test_api_gateway_event(
headers=create_headers(),
query_string_parameters={
Copy link
Contributor

@katebobyn-nhs katebobyn-nhs May 22, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If I'm reading this right, the test is

  1. Creating a pointer of type: MHCP, cat: Care Plan
  2. Creating a pointer of type: NEWS2, cat: Obs
  3. Searching for pointers of type: MHCP, cat: Care Plan
    It then expects the one result (pointer 1) since pointer 2 would be filtered out by both criteria.

I think to prove both filters are being applied there needs to be a test scenario where, e.g., you search for type: MHCP, cat: Obs
Then the expected result is an empty searchset bundle because 1 is filtered out on the basis of failure to match category, and 2 is filtered out on the basis of failure to match type.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah I'll add that I'll also add searching with multiple categories and the one type to show that the optimisation for the single type is still used and that it wont get other categories even if they're provided because it isnt for that type

@katebobyn-nhs
Copy link
Contributor

Can we add feature tests?

@eesa456
Copy link
Contributor Author

eesa456 commented May 23, 2025

Can we add feature tests?

There are already some feature tests I wrote back when I did the category filter work but I can do an additional scenario that is basically the unit test you mentioned above but an integration test

@github-actions
Copy link

🚀 PR environment successfully deployed.
Commit Hash: cb69b2c7d1759df23229bc4c3e033e52bbf56177
URL: https://nrl1205-3a0f35.api.record-locator.dev.national.nhs.uk/

@github-actions
Copy link

github-actions bot commented Jun 3, 2025

🚀 PR environment successfully deployed.
Commit Hash: aba621417a7b24fc799ce9f8d97a9149525509cd
URL: https://nrl1205-3a0f35.api.record-locator.dev.national.nhs.uk/

@sonarqubecloud
Copy link

sonarqubecloud bot commented Jun 6, 2025

@github-actions
Copy link

github-actions bot commented Jun 6, 2025

🚀 PR environment successfully deployed.
Commit Hash: 717b2c327b32d8d3b0342c8858a8dcc1008d8422
URL: https://nrl1205-3a0f35.api.record-locator.dev.national.nhs.uk/

Copy link
Contributor

@mattdean3-nhs mattdean3-nhs left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM 👍

@mattdean3-nhs mattdean3-nhs merged commit 497bbc6 into develop Jun 6, 2025
9 checks passed
@mattdean3-nhs mattdean3-nhs deleted the feature/eema1-NRL-1205-categoryIsntIgnoredInSearch branch June 6, 2025 09:39
@github-actions
Copy link

github-actions bot commented Jun 6, 2025

💥 Something went wrong while destroying the pull request environment.
Check Output Logs

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants