Remove autoscan ITs and add withoutSemantic tests

.github/workflows/build.yml

@@ -360,82 +360,13 @@ jobs:
             -DuseMissingFile \
             "-Dlicense.overrideUrl=file://${PWD}/override-dep-licenses.properties"
 
+  # TODO: Remove this no-op job once an admin removes "Autoscan Tests" from the required checks.
+  # The autoscan integration tests have been replaced by withoutSemantic() unit tests.
   autoscan:
     name: Autoscan Tests
-    needs:
-      - build
-    if: ${{ needs.build.outputs.deployed }}
-    runs-on: sonar-m-public
-    permissions:
-      id-token: write
-      contents: write
-    env:
-      BUILD_NUMBER: ${{ needs.build.outputs.build-number }}
-      SQ_VERSION: LATEST_RELEASE
+    runs-on: ubuntu-latest
     steps:
-      - uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
-      # For now, the autoscan job need to execute two mvn commands:
-      #   * The build of java-checks-test-sources module which requires Java 24.
-      #   * The tests using Orchestrator and SonarQube that, for now, fail to work using Java 24
-      - uses: jdx/mise-action@9e7f7633ff6f6d6048a9418a68d48f288f50eb14 # v4.2.3
-        with:
-          version: 2026.7.18
-      - uses: SonarSource/vault-action-wrapper@v3
-        id: secrets
-        with:
-          secrets: |
-            development/kv/data/next url | SONAR_HOST_URL;
-            development/kv/data/next token | SONAR_TOKEN;
-            development/github/token/licenses-ro token | GITHUB_TOKEN;
-      - name: Ensure Separate Job Cache Key
-        uses: ./.github/actions/write-file
-        with:
-          file-path: target/just_for_cache_key_calculation/pom.xml
-          content: ${{ github.job }}
-      - uses: SonarSource/ci-github-actions/config-maven@v1
-        with:
-          artifactory-reader-role: private-reader
-          use-develocity: ${{ env.USE_DEVELOCITY }}
-          develocity-url: ${{ env.DEVELOCITY_URL }}
-      - name: Compile Test Sources
-        env:
-          SONAR_HOST_URL: ${{ fromJSON(steps.secrets.outputs.vault).SONAR_HOST_URL }}
-          SONAR_TOKEN: ${{ fromJSON(steps.secrets.outputs.vault).SONAR_TOKEN }}
-        working-directory: java-checks-test-sources
-        run: |
-          mvn clean compile test-compile --batch-mode
-      - name: Select Java 21
-        shell: bash
-        run: |
-          mise use java@21
-          JAVA_21_HOME="$(mise where java@21)"
-          echo "JAVA_HOME=${JAVA_21_HOME}" >> "$GITHUB_ENV"
-          echo "${JAVA_21_HOME}/bin" >> "$GITHUB_PATH"
-      - name: Orchestrator Cache
-        uses: ./.github/actions/orchestrator-cache
-        with:
-          sq-version: ${{ env.SQ_VERSION }}
-      - name: Run autoscan tests
-        env:
-          SONAR_HOST_URL: ${{ fromJSON(steps.secrets.outputs.vault).SONAR_HOST_URL }}
-          SONAR_TOKEN: ${{ fromJSON(steps.secrets.outputs.vault).SONAR_TOKEN }}
-          GITHUB_TOKEN: ${{ fromJSON(steps.secrets.outputs.vault).GITHUB_TOKEN }}
-        working-directory: its/autoscan
-        run: >
-          mvn clean package --batch-mode --errors --show-version
-          --activate-profiles it-autoscan
-          -Dsonar.runtimeVersion="$SQ_VERSION"
-          -Dmaven.test.redirectTestOutputToFile=false
-          -Dparallel=methods
-          -DuseUnlimitedThreads=true
-      - name: Upload Actual Results On Failure
-        if: failure()
-        uses: ./.github/actions/upload-actual
-        with:
-          name: autoscan
-          it-dir: its/autoscan
-          expected-dir: src/test/resources/autoscan/diffs
-          actual-dir: target/actual/autoscan-diffs
+      - run: echo "Autoscan tests have been removed. This job is a no-op until the required check is removed by an admin."
 
   qa-os-win:
     name: Build and Unit Test on Windows
@@ -473,7 +404,6 @@ jobs:
       - sanity
       - test-analyze
       - custom-rules-license-check
-      - autoscan
       - qa-os-win
     if: ${{ needs.build.outputs.deployed }}
     runs-on: sonar-s-public

README.md

@@ -155,47 +155,6 @@ For example using the command:
 
     cp its/ruling/target/actual/* its/ruling/src/test/resources/
 
-#### Autoscan Test
-
-The tests in the [autoscan module](its/autoscan) are designed to detect differences between the issues the Java analyzer can find with and without bytecode.
-The goal here is to spot and fix the potential FPs, and verify the expected FNs between that would show up in [SonarQube Cloud's automatic analysis](https://docs.sonarsource.com/sonarqube-cloud/advanced-setup/automatic-analysis/).
-
-Running this test can be broken down in 2 steps:
-
-1. Compiling the test sources
-2. Executing the autoscan test
-
-##### Compiling the test sources
-
-Make sure that the `java-checks-test-sources` module has been compiled (ie: the .class files in `java-checks-test-sources/target/` are up to date).
-
-In doubt, go the [`java-checks-test-sources`](java-checks-tests-sources) module and run:
-```shell
-# Use java 26!
-mvn clean compile
-```
-
-##### Executing the autoscan test
-
-To run the tests, move to the [`its/autoscan`](its/autoscan) folder and run:
-```shell
-# cd its/autoscan
-# use Java 21!
-mvn clean package --batch-mode --errors --show-version \
-   --activate-profiles it-autoscan \
-  -Dsonar.runtimeVersion=LATEST_RELEASE
-```
-
-The artifacts produced during the test execution will be found in [`its/autoscan/target/actual`](its/autoscan/target/actual).
-You will want to compare the results produced in the autoscan-diff-by-rules
-
-For more detailed information, you can compare the differences between the results found with bytecode and without bytecode by comparing two respective folders:
-* [java-checks-test-sources-mvn](its/autoscan/target/actual/java-checks-test-sources-mvn)
-* [java-checks-test-sources-no-binaries](its/autoscan/target/actual/java-checks-test-sources-no-binaries)
-
-Depending on the results found, you might need to update the ground truth.
-The expected results are listed in [src/test/resources](its/autoscan/src/test/resources/autoscan/diffs).
-
 #### Debugging Integration Tests
 You can debug ITs by adding `-Dmaven.binary=mvnDebug` as an option when running the tests. This will cause the analyzer JVM to wait for a debugger to be attached before continuing.