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
There is already some support on JUnit/TestNG methods to navigate to non-Java DSL test source files. The inverse could be supported as well.
Tasks
Implement an action that would navigate from a YAML test file to its corresponding JUnit/TestNG method.
The action could be assigned the Ctrl+Shift+T (on Windows) shortcut, the same one can navigate back and forth between source and test files in Java code.
Take into account if there are more than one JUnit/TestNG method covering the YAML file. In that case show a list of the matching methods, so that users can select which one to navigate to.
NOTE: this may also help uncover that a YAML test is executed multiple times by multiple methods.
The action would work only for files that are actual Citrus YAML tests.
For this, all @CitrusTestSource annotations in the project must be examined and indexed in some way, so that they can be properly matched to YAML files.
Scope
Only the YAML DSL is in scope for this issue. XML and Groovy DSLs will be handled in separate issues.
The text was updated successfully, but these errors were encountered:
Summary
There is already some support on JUnit/TestNG methods to navigate to non-Java DSL test source files. The inverse could be supported as well.
Tasks
@CitrusTestSource
annotations in the project must be examined and indexed in some way, so that they can be properly matched to YAML files.Scope
The text was updated successfully, but these errors were encountered: