Althought there is run line marker to run yaml test files, at the moment it doesn't recognize non-classpath resources in the sources attribute of the @CitrusTestSource annotation. Also, the lookup logic might fail to recognize a test method as matching for any reason.
To improve on these cases, a separate action would be useful, with which users could choose an arbitrary @CitrusTestSource test method they would like to execute the current file with.
Tasks
Create a new action to run an arbitrary test method, and add this action to the yaml run line marker.
Either
present a list of test classes to the user to select from, and then separately the @CitrusTestSource methods from that class, or
present the list of all @CitrusTestSource methods in the project in one go.
The gradle task selection popup must work here too.
picimako
commented
5 months ago
Summary
Althought there is run line marker to run yaml test files, at the moment it doesn't recognize non-classpath resources in the
sourcesattribute of the@CitrusTestSourceannotation. Also, the lookup logic might fail to recognize a test method as matching for any reason.To improve on these cases, a separate action would be useful, with which users could choose an arbitrary
@CitrusTestSourcetest method they would like to execute the current file with.Tasks
@CitrusTestSourcemethods from that class, or@CitrusTestSourcemethods in the project in one go.