feat: support multiple test source sets (e.g. Gradle integrationTest suite)

[jimisola]

Problem

The plugin assumes a single test source set, which matches Maven's model. In Gradle projects that use multiple test source sets (e.g. a separate integrationTest JvmTestSuite), the annotation processor runs once per compilation task and produces one annotations.yml per source set:

Compilation task	Annotation output
compileJava	build/generated/sources/annotationProcessor/java/main/resources/annotations.yml
compileTestJava	build/generated/sources/annotationProcessor/java/test/resources/annotations.yml
compileIntegrationTestJava	build/generated/sources/annotationProcessor/java/integrationTest/resources/annotations.yml

RequirementsToolExtension only exposes a single svcsAnnotationsFile (RegularFileProperty), hardcoded by default to the test source set output. The integrationTest annotations are silently ignored.

Impact: @SVCs annotations placed on integration test methods are never picked up by reqstool status, resulting in artificially low SVC coverage even when tests exist.

Root cause

RequirementsToolExtension.java (line 49):

this.svcsAnnotationsFile.convention(project.getLayout()
    .getBuildDirectory()
    .file("generated/sources/annotationProcessor/java/test/resources/annotations.yml"));

RequirementsToolTask.execute() reads a single file:

File svcsAnnotFile = svcsAnnotationsFile.getAsFile().getOrNull();
if (svcsAnnotFile != null && svcsAnnotFile.exists()) {
    testsNode = yamlMapper.readTree(svcsAnnotFile).path(XML_REQUIREMENT_ANNOTATIONS).path(XML_TESTS);
}

Proposed fix

1. Change svcsAnnotationsFile (RegularFileProperty) → svcsAnnotationsFiles (ConfigurableFileCollection) in both RequirementsToolExtension and RequirementsToolTask
2. Default the collection to all known test-scope annotation outputs (auto-discover JvmTestSuite source sets, or at minimum include test + any additional suites)
3. In RequirementsToolTask.execute(), merge all tests nodes from all provided files (deep-merge by SVC ID, concatenating the entry lists)

Backwards compatible: a single-file config still works; multi-suite projects get correct coverage without workarounds.

Workaround

Currently requires a custom Gradle task to merge the two annotation files before passing the result to svcsAnnotationsFile — an unnecessary build-script burden.

[jimisola]

Test fixture must be updated to reproduce the bug

The fixture project at tests/fixtures/test_project currently only has a single test source set. To reproduce and verify the fix, it needs an integrationTest JvmTestSuite with @SVCs-annotated tests.

Required changes to tests/fixtures/test_project/build.gradle

The fixture build.gradle should be updated from:

plugins {
    id 'java'
    id 'io.github.reqstool.gradle-plugin' version '0.1.0'
}

dependencies {
    testAnnotationProcessor 'io.github.reqstool:reqstool-java-annotations:1.0.0'
}

test {
    useJUnitPlatform()
}

requirementsTool {
    datasetPath = file('docs/reqstool')
    testResults = ['build/test-results/**/*.xml']
}

tasks.named('assembleRequirements') {
    dependsOn tasks.named('test')
}

To something like this (pattern from a real multi-suite project):

plugins {
    id 'java'
    id 'io.github.reqstool.gradle-plugin' version '0.1.0'
}

dependencies {
    implementation 'io.github.reqstool:reqstool-java-annotations:1.0.0'
    annotationProcessor 'io.github.reqstool:reqstool-java-annotations:1.0.0'
    testCompileOnly 'io.github.reqstool:reqstool-java-annotations:1.0.0'
    testAnnotationProcessor 'io.github.reqstool:reqstool-java-annotations:1.0.0'
}

testing {
    suites {
        test {
            useJUnitJupiter()
        }

        integrationTest(JvmTestSuite) {
            sources {
                java {
                    srcDirs = ['src/integration-test/java']
                }
            }
            dependencies {
                implementation project()
            }
            targets {
                all {
                    testTask.configure {
                        shouldRunAfter(test)
                    }
                }
            }
        }
    }
}

configurations {
    integrationTestImplementation.extendsFrom implementation, testImplementation
    integrationTestCompileOnly.extendsFrom compileOnly, testCompileOnly
    integrationTestAnnotationProcessor.extendsFrom annotationProcessor, testAnnotationProcessor
    integrationTestRuntimeOnly.extendsFrom runtimeOnly, testRuntimeOnly
}

tasks.named('check') {
    dependsOn(testing.suites.integrationTest)
}

requirementsTool {
    datasetPath = file('docs/reqstool')
    testResults = ['build/test-results/**/*.xml']
}

tasks.named('assembleRequirements') {
    dependsOn test
}

Add an integration test with @SVCs

Add src/integration-test/java/io/github/reqstool/example/HelloIT.java with at least one @SVCs-annotated method covering an SVC defined in the fixture's software_verification_cases.yml. After the fix, reqstool status must show that SVC as covered.

What the test should assert

After ./gradlew assembleRequirements, build/reqstool/annotations.yml must contain the SVC IDs from both src/test and src/integration-test annotation processors. Currently only src/test SVCs appear.