You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Based on the extensions of #42988, there were ideas to extend the Continuous Testing Feature with a possibility to
select tags or class names for test execution during runtime
filter the Continuous Testing table in the Dev UI (execute all tests, but only show filtered entries)
Important
We have to be aware that there are already application properties to include and exlude tags and patterns.
Implementation ideas
To restrict the test execution, I would suggest to use the properties. They are powerful and well-documented - and can be changed in the Dev UI during runtime. I would suggest to only extend the documentation for this.
What about filtering? Is there a need for a filter text, that automatically filters based on the users input? (e.g. filtering tags, class names and display names, being CamelCase-aware for the class names)
The text was updated successfully, but these errors were encountered:
Description
Based on the extensions of #42988, there were ideas to extend the Continuous Testing Feature with a possibility to
Important
We have to be aware that there are already application properties to include and exlude tags and patterns.
Implementation ideas
To restrict the test execution, I would suggest to use the properties. They are powerful and well-documented - and can be changed in the Dev UI during runtime. I would suggest to only extend the documentation for this.
What about filtering? Is there a need for a filter text, that automatically filters based on the users input? (e.g. filtering tags, class names and display names, being CamelCase-aware for the class names)
The text was updated successfully, but these errors were encountered: