When your test suite grows to dozens or hundreds of test cases, scrolling through the list becomes painful. You know the test exists, but finding it? That's where time goes to die. That's why we built search and filtering for test cases in Probefish.
The Problem with Growing Test Suites
A small test suite is easy to manage:
Test Case 1: Basic greeting
Test Case 2: Error handling
Test Case 3: Edge case - empty input
But real projects grow fast:
47 test cases across login, checkout, support, onboarding...
Some are suspended for debugging
Some are tagged "regression", others "smoke-test"
You need to run just the payment-related ones
Scrolling through 47 test cases to find "that one about refunds" isn't testing - it's archaeology.
What We Built
The test case list now includes real-time search and filtering with three powerful tools:
1. Text Search
Search across multiple fields simultaneously:
- Name - Find "refund" in test case names
- Tags - Search for tests tagged "api" or "critical"
- Input values - Find tests using specific variable values
- Expected output - Search by expected results
- Notes - Find tests by their descriptions
Just start typing - results filter instantly.
2. Status Filter
Quick dropdown to show:
- All - Every test case
- Enabled - Only active tests
- Suspended - Only paused tests
Perfect for reviewing which tests are temporarily disabled, or focusing on what's currently running.
3. Tag Filter
Multi-select filtering by tags:
- Select one or more tags
- Shows test cases matching any selected tag
- See at a glance how many tests match
Tags like smoke-test, regression, critical, wip become powerful organization tools.
Real-World Use Cases
1. Pre-Deployment Smoke Tests
You have 200 test cases, but only 15 are tagged smoke-test for quick pre-deployment checks.
Filter: Tags → "smoke-test"
Result: 15 test cases shown
Action: Select all → Run selected
Why it matters: Run critical tests in 2 minutes instead of waiting for the full suite.
2. Debugging a Specific Feature
Something's broken in checkout. You need to find and run all checkout-related tests.
Search: "checkout"
Result: 8 test cases about checkout flow
Or if you've been disciplined with tags:
Filter: Tags → "checkout", "payment"
Result: 12 test cases across related features
Why it matters: Focus your debugging on relevant tests, not the entire suite.
3. Reviewing Suspended Tests
Before a release, you want to make sure no important tests are accidentally suspended.
Filter: Status → "Suspended"
Result: 3 test cases shown
Review: "Oh, I suspended these during debugging last week"
Action: Re-enable and run
Why it matters: Suspended tests are easy to forget. Regular review prevents gaps in coverage.
4. Finding Tests by Input Data
You remember writing a test that uses a specific API key or test user:
Search: "test-user-premium"
Result: 2 test cases using that test account
Input values are searchable, so you can find tests by the data they use.
Why it matters: When test data changes, find every test that needs updating.
5. Organizing Large Regression Suites
Your regression suite has grown organically. Time to understand what you have:
Filter: Tags → "regression"
Count: "Showing 45 of 120 test cases"
Filter: Tags → "api"
Count: "Showing 28 of 120 test cases"
Filter: Status → "Suspended"
Count: "Showing 7 of 120 test cases"
Why it matters: Understand your test coverage distribution without manually counting.
6. Combining Filters
Filters stack together for precise targeting:
Search: "error"
+ Status: "Enabled"
+ Tags: "api"
Result: "Showing 4 of 120 test cases"
Only enabled API tests with "error" in their name, inputs, or notes.
Why it matters: Complex queries become simple filter combinations.
Smart Selection Behavior
The "Select All" checkbox is filter-aware:
- No filters: Selects all enabled test cases
- With filters: Selects only visible filtered test cases
- Deselect: Only deselects visible cases (keeps hidden selections)
This means you can:
- Filter to "checkout" tests → Select all
- Clear filter → Filter to "payment" tests → Select all
- Clear filter → Run all selected (checkout + payment tests)
Build up selections across multiple filter views.
Drag-and-Drop Protection
When filters are active, drag-and-drop reordering is disabled.
Why? Reordering a filtered view is confusing. If you're viewing 10 of 50 test cases, dragging one would reorder it among all 50 - not what you expect.
Clear filters to reorder test cases.
Getting Started
- Open any test suite with test cases
- Use the search box to filter by text
- Use the status dropdown to filter by enabled/suspended
- Use the tag filter (if you have tagged tests) to filter by tags
- Check the count - "Showing X of Y test cases"
- Clear filters with one click when done
Pro Tips
Tag Naming Conventions
Establish consistent tag patterns for your team:
| Tag | Meaning |
|---|---|
smoke |
Fast, critical tests for every deploy |
regression |
Full test coverage |
wip |
Work in progress, expect failures |
slow |
Tests that take longer than usual |
flaky |
Known intermittent failures |
critical |
Must pass for release |
Suspend vs Delete
Don't delete test cases you might need later. Suspend them instead:
- Filter to suspended tests periodically
- Review if they're still needed
- Re-enable or delete with confidence
Search Shorthand
The search box is forgiving:
- Case-insensitive: "Login" matches "login"
- Partial matches: "check" matches "checkout"
- Searches multiple fields: One query, all matches
Conclusion
Test suites should grow as your product grows. But that growth shouldn't slow you down. Search and filtering transform a wall of test cases into an organized, navigable library.
Find the test you need. Run what matters. Ship with confidence.
Start organizing your test cases today with Probefish.