Skip to content
This repository was archived by the owner on Sep 11, 2025. It is now read-only.

ui/search: CVEs to Vulnerabilities, tabs, multiple Downloads#49

Closed
queria wants to merge 3 commits intotrustification:mainfrom
queria:search-cve-vulnerability
Closed

ui/search: CVEs to Vulnerabilities, tabs, multiple Downloads#49
queria wants to merge 3 commits intotrustification:mainfrom
queria:search-cve-vulnerability

Conversation

@queria
Copy link
Copy Markdown
Collaborator

@queria queria commented Apr 2, 2025

Update Search scenario to match implementation in trustify v2.

Main point is the CVEs are labeled Vulnerabilities instead.

Also there is currently:

  • not a single list of results but still tabs by type
  • download links is instead menu with one or more links inside

There was mistake with mixed up 'Example' blocks
between/after scenarios outlines:

  • User toggles the list and manipulates the list
  • Download Links on the Search Result list so while updating them moved the example block to correct place.

Related to: TC-2191

queria added 3 commits April 23, 2025 04:12
Update Search scenario to match implementation in trustify v2.

Main point is the CVEs are labeled Vulnerabilities instead.

Also there is currently:
- not a single list of results but still tabs by type
- download links is instead menu with one or more links inside

There was mistake with mixed up 'Example' blocks
between/after scenarios outlines:
- User toggles the <types> list and manipulates the list
- Download Links on the <types> Search Result list
so while updating them moved the example block to correct place.

Related to: TC-2191
@queria queria force-pushed the search-cve-vulnerability branch from 1219971 to 8ccff45 Compare April 23, 2025 02:12
@matejnesuta matejnesuta self-requested a review April 28, 2025 10:49
Copy link
Copy Markdown
Collaborator

@matejnesuta matejnesuta left a comment

Choose a reason for hiding this comment

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

Honestly, I would close this PR instead of merging. I have done almost identical changes to the Gherkin during work on UI automation and I think this could cause unnecessary merge conflitcs.

@queria
Copy link
Copy Markdown
Collaborator Author

queria commented Aug 19, 2025

I see, so this change can be ignored, expected to be covered by PR #66

@queria queria closed this Aug 19, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants