Result Filters, Filter Templates, Testcase Conditions, and Unresolved Pipe-In Detection
Survey Tester provides powerful filtering capabilities to help you find and analyze issues, test runs, pages, and translations. Filters can combine criteria from test runs, issues, classifications, role visibility, and survey answers using logical groups such as ALL, ANY, and NONE.
This release also introduces:
- Reusable result filter templates for new projects
- Enhanced testcase conditions using the same filter editor
- Automatic Unresolved Pipe-In Detection for broken survey piping references
More Flexible Result Filters
When to Use This Feature
Use result filters when you need to
- Find specific issues or test runs
- Analyze results by language, market, tester, browser, or other attributes
- Create complex searches using multiple conditions
- Exclude specific data sets
- Work with survey response data alongside test run information
How Result Filters Work: Filters are built from one or more criteria.
- Each criterion is defined on a separate row.
- By default, all criteria must match.
- Criteria can be organized into groups using:
- ALL = every criterion must match
- ANY = at least one criterion must match
- NONE = no criteria may match
- Groups can be nested to create advanced filter logic.
While building a filter, Survey Tester continuously builds the query statement test runs.
Creating a Filter
- Open the filter editor.
- Add a criterion using one of the quick-add buttons: Language, Market, Testcase, Milestone or select from the drop list
- Select if the filter to be based on Test Runs or Survey Anwsers.
- Select the required operator.
- Choose one or more values.
- Add additional criteria as needed.
- Optionally create groups using ALL, ANY, or NONE.
- Review the match count displayed below the filter.
- Save or apply the filter.
Available Filter Criteria
Filters can compare the following data:
Test Run Fields:
- Language
- Market
- Testcase
- Milestone
- Run date
- Browser
- Operating system
- Tester
- Test link
- Run Finished
Issue Fields: Available on the Issues page only.
Classification Fields: Custom classification values associated with issues and test runs.
Role Visibility: Controls filtering based on visibility settings.
Survey Answers
A filter can use survey answers as criteria.
- On the Issues page, the answer used is the answer that existed when the issue was reported.
- On all other pages, the answer used is the latest answer recorded for the test run.
Multi-Value Criteria: The operators = and ≠ support multiple values in a single criterion.
Language = English, German, French
Matches rows where the language is either English, German, or French.
Market ≠ UK, US
Matches rows that are neither UK nor US.
Notes and Limitations
Missing Values: Negative comparisons such as:
- ≠
- Doesn't contain
also match rows where no value exists.
Auto-Detected Issues: Technical issues created by automatic detections are included in results by default.
To hide them, add:
Auto-detected = No
Page Support
The same filter can be used on:
- Issues
- Test runs
- Pages
- Translations
Criteria that only apply to issues are clearly marked when used on other pages.
Result Filter Templates for New Projects
Filter templates allow frequently used filters to be automatically added when a new project is created.
Use filter templates when your organization regularly uses the same filters across multiple projects.
Creating a New Project with Filter Templates
- Create a new project.
- Select the desired folder.
- Select the project template.
- Review the available filter templates.
- Tick the templates you want to add to the project.
- Complete project creation.
Testcase Conditions
Testcase conditions now use the same editor and logic as result filters.
Use testcase conditions to control when a testcase is applicable based on project or respondent attributes.
Creating a Testcase Condition
- Open the testcase.
- Add or edit a condition.
- Create criteria using the filter editor.
- Select the operator and values.
- Save the testcase.
Example: A single condition can contain multiple values:
Region = North, South
The testcase will apply when the region is either North or South.