---
title: "Verify intersecting search filters"
description: "Test that combining an owner filter with a status filter returns their intersection and preserves the query when one constraint is removed."
canonical_url: "https://vostride.com/agent-library/search-filtering/intersect-status-and-owner.md"
md_url: "https://vostride.com/agent-library/search-filtering/intersect-status-and-owner.md"
content_kind: "recipe"
topic: "search-filtering"
---

# Verify intersecting search filters

Test that combining an owner filter with a status filter returns their intersection and preserves the query when one constraint is removed.

## Risk

A filter toolbar can display both selected values while the backend applies only the most recently changed constraint. Seed near matches deliberately so a broad result cannot accidentally satisfy this journey.

## Fixtures

- A test-owned project contains Orion open owned by Ada, Lyra closed owned by Ada, and Vega open owned by Bo.
- A separate unfiltered inventory records all three stable issue keys and their statuses before the run.
- The QA member can view every seeded issue, and no background automation changes their ownership.

## Steps

1. Open the project issue list and verify all three fixture titles are present before applying filters.
2. Choose owner Ada and verify Orion and Lyra appear while Vega does not.
3. Add status Open and verify Orion is the sole result, with its stable key visible.
4. Remove only the owner filter and verify Orion and Vega appear while Lyra remains absent.
5. Clear status and verify the original three-record inventory is restored with no remaining filter chips.

## Expected results

- The intersection contains exactly the Orion key; matching a title substring alone is insufficient.
- The Open-only result contains two known keys, independent of visual row ordering.
- The fixture inventory remains unchanged after filtering, because this journey is read-only.

## False-pass traps

- A chip with the correct label can coexist with unfiltered rows; inspect membership after every change.
- An empty list is not proof of correct exclusion unless the expected positive record is also visible.

## Cleanup

- Remove test-owned issue fixtures after evidence is collected.
- Reset persisted list filters for this QA account.

## Use with agent-qa

Adapt this test design to your application's acceptance criteria and configured target using the [recipe execution guide](/agent-library/software-factory/turn-a-recipe-into-an-agent-qa-test.md). External fixture setup and non-UI checks require your own supported hooks or test tooling. Validate the authored test, execute it, and inspect the completed evidence; this recipe is not a recorded test result.

## References

- [agent-qa test](/docs/agent-qa/configuration/test.md)
- [agent-qa first test](/docs/agent-qa/guides/first-test.md)
- [agent-qa web testing](/docs/agent-qa/guides/web-testing.md)

- [Search and filtering QA recipes](/agent-library/search-filtering.md)
- [Software factory QA library](/agent-library.md)