CarlosJuncher03 commented on issue #7890: URL: https://github.com/apache/hop/issues/7890#issuecomment-5332316419
I think the confusion comes from the terminology I used. When I said "test pipelines", I was referring to **Pipeline Unit Tests attached to a pipeline**, not to separate pipelines that are specifically "test pipelines". In my case, I have one reusable pipeline that simulates the logic of a `MERGE`. It receives different SQL files, variables, and metadata depending on the production pipeline being validated. Because of that, I created multiple **Pipeline Unit Tests for that same reusable pipeline**, with each unit test representing a different production scenario/configuration. The issue I'm trying to describe is simply that, when a single pipeline has many Pipeline Unit Tests attached to it, the unit test selector becomes difficult to navigate. A simpler improvement might be to make the existing selector searchable/type-to-filter, so typing part of the unit test name filters the list in real time. This would avoid adding another management screen or significantly changing the current UI. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
