@CitrusTestSource annotated methods reference test scripts and test descriptor files in other DSLs. To make the lookup and navigation to those files simpler and quicker, some kind of navigation option should be implemented.
Tasks
The first option is a line marker, but considering that there can be multiple files and locations specified and in multiple ways, there may need to be a distinction, and separate options to navigate to them separately.
The sources attribute will support only classpath resource paths, for now.
Combination of options
File extensions
XML, SPRING: .xml
YAML: .yaml
GROOVY: .groovy
name
packageName
packageScan
sources
Executed
Java test method name in package of the declaring class.
+
name attribute value + file extension of type in package of the declaring class.
+
Java test method name in the packageName package.
+
The Java test method name is ignored. Test names are the ones found in the packageScan package.
+
The files specified in sources in the packages of files specified in sources
+
+
name attribute value + file extension of type in packageName package.
+
+
name attribute value + file extension of type from the current package, AND all tests in the packageScan package.
+
+
Only the files specified in sources, but a GroovyTestLoader is also created for name which is not executed.
+
+
Only the files found in packageScan.
+
+
+
name attribute value + file extension of type from the packageName package, AND all tests in the packageScan package.
+
+
Only the files specified in sources.
+
+
+
Only the files specified in sources, but a GroovyTestLoader is also created for name which is not executed.
+
+
Files found in packageScan, AND in source.
+
+
+
Only the name attribute value + file extension of type from the current package but GroovyTestLoaders are also created for packageScan and sources that are not executed.
+
+
+
Only the files specified in packageScan and sources.
+
+
+
+
name attribute value + file extension of type from the packageName package, AND sources, but GroovyTestLoaders are also created for packageScan which are not executed.
picimako
commented
1 year ago
Summary
@CitrusTestSourceannotated methods reference test scripts and test descriptor files in other DSLs. To make the lookup and navigation to those files simpler and quicker, some kind of navigation option should be implemented.Tasks
sourcesattribute will support only classpath resource paths, for now.Combination of options
nameattribute value + file extension oftypein package of the declaring class.packageNamepackage.packageScanpackage.sourcesin the packages of files specified insourcesnameattribute value + file extension oftypeinpackageNamepackage.nameattribute value + file extension oftypefrom the current package, AND all tests in thepackageScanpackage.sources, but a GroovyTestLoader is also created fornamewhich is not executed.packageScan.nameattribute value + file extension oftypefrom thepackageNamepackage, AND all tests in thepackageScanpackage.sources.sources, but a GroovyTestLoader is also created fornamewhich is not executed.packageScan, AND insource.nameattribute value + file extension oftypefrom the current package but GroovyTestLoaders are also created forpackageScanandsourcesthat are not executed.packageScanandsources.nameattribute value + file extension oftypefrom thepackageNamepackage, ANDsources, but GroovyTestLoaders are also created forpackageScanwhich are not executed.