allure-framework / allure-framework/allure2

Search in test parameters

Open
#805 2 comments 3 reactions 0 assignees View on GitHub
Dominant language
HTML
Stars
5.5k
Forks
782
Avg merge
2d 33m
Merged PRs (30d)
16

Description

#### I'm submitting a ...
- [ ] bug report
- [x] feature request
- [ ] support request => Please do not submit support request here, see note at the top of this template.

#### What is the current behavior?

Now search field is applied only to test names (not to parameters).

![Demo report](https://i.imgur.com/kCFa6mE.png)
![Current search](https://i.imgur.com/Xq4H8xg.png)

#### What is the expected behavior?

It is useful to search inside test parameters along with test names.
For example, I expect to see `#2 testFour null, null, some-value, null` in the second screenshot above (search `some`).

#### What is the motivation / use case for changing the behavior?

We use browser name as test parameter. And I'd like to filter only one browser, for example.

#### Please tell us about your environment:

Allure version: 2.6.0

Contributor guide

Open the contributing guide

Research direction

No source file or test is named in the issue. Reproduce the report search with a parameter such as `some-value`, then trace the existing test-name search entry point and verify that matching parameter text appears in the filtered results while existing name search still works.

Written by the indexing model from the issue text.

Assessment

Tech stack
html
Domain
frontend
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.