chore: Remove old integ test code. (#502)

Signed-off-by: Karthik Bekal Pattathana <133984042+karthikbekalp@users.noreply.github.com>

Author: karthikbekalp

.github/PULL_REQUEST_TEMPLATE.md

@@ -23,7 +23,6 @@ See [DEVELOPMENT.md](https://github.com/aws-deadline/deadline-cloud-for-cinema-4
 
 - Have you made changes to the submitter?
 If yes, please include the results of both the automated tests and any manual tests that you ran.
-Also, check if there is a change to the `integ_test_helpers.py` file within cinema4d_submitter as a result of your submitter change.
 *delete text ending here* 
 
 ### Was this change documented?
@@ -51,4 +50,4 @@ please ensure that the title of your commit follows our conventional commit guid
 
 ----
 
-*By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.*
+*By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.*

.github/workflows/integ_macos.yml

@@ -64,8 +64,8 @@ jobs:
           # Create the hatch environment first so that pip's install output
           # (which can include marker-mismatch messages containing quotes)
           # doesn't pollute the captured Python path below.
-          hatch env create integ-xa11y
-          HATCH_PYTHON=$(hatch -e integ-xa11y run python -c "import os,sys; print(os.path.realpath(sys.executable))")
+          hatch env create integ
+          HATCH_PYTHON=$(hatch -e integ run python -c "import os,sys; print(os.path.realpath(sys.executable))")
           SETUP_PYTHON=$(python3 -c "import os,sys; print(os.path.realpath(sys.executable))")
           for BIN_PATH in "$SETUP_PYTHON" "$HATCH_PYTHON"; do
             sudo sqlite3 "/Library/Application Support/com.apple.TCC/TCC.db" \
@@ -151,7 +151,7 @@ jobs:
           echo "SSM_SESSION_ID=$ssmSessionId" >> "$GITHUB_ENV"
           echo "SSM session id: ${ssmSessionId:-<not captured>}"
 
-          hatch run integ-xa11y:test
+          hatch run integ:test
 
       - name: Tear down
         if: always()

.github/workflows/integ_windows.yml

@@ -133,7 +133,7 @@ jobs:
           "SSM_SESSION_ID=$ssmSessionId" | Out-File -FilePath $env:GITHUB_ENV -Append -Encoding utf8
           if ($ssmSessionId) { Write-Host "SSM session id: $ssmSessionId" } else { Write-Host "SSM session id: <not captured>" }
 
-          hatch run integ-xa11y:test
+          hatch run integ:test
 
       - name: Tear down
         if: always()

.github/workflows/integration_tests.yml

@@ -29,7 +29,7 @@ jobs:
 
   UnitTests:
     needs: [TagRelease]
-    name: Unit and Integration Tests
+    name: Unit Tests
     uses: ./.github/workflows/code_quality.yml
     with:
       tag: ${{ needs.TagRelease.outputs.tag }}
@@ -66,13 +66,6 @@ jobs:
       id-token: write
       contents: read
 
-  ManualTestGate:
-    needs: [TagRelease, BuildInstaller]
-    runs-on: ubuntu-latest
-    environment: release-gate
-    steps:
-      - run: echo "Manual testing approved for ${{ needs.TagRelease.outputs.tag }}"
-
   PreRelease:
       needs: [TagRelease, UnitTests, Xa11yWindows, Xa11yMacOS]
       uses: aws-deadline/.github/.github/workflows/reusable_prerelease.yml@mainline
@@ -116,7 +109,7 @@ jobs:
          :
   
   ReleaseInstaller:
-    needs: [TagRelease, IsCondaReady, ManualTestGate]
+    needs: [TagRelease, IsCondaReady]
     uses: aws-deadline/.github/.github/workflows/reusable_release_installers.yml@mainline
     secrets: inherit
     permissions:

.github/workflows/release_publish.yml

@@ -11,13 +11,7 @@ __pycache__/
 
 /dependency_bundle/
 /dev_install/
-/job_bundle_output_tests/*/scene/renders
-/job_bundle_output_tests/*/scene/*.c4d
-/job_bundle_output_tests/*/scene/*.deadline_render_settings.json
-/job_bundle_output_tests/*/scene/tex
-/job_bundle_output_tests/*/*.psd
-/test/integ/**/generated_bundle/*
-/test/integ_xa11y/**/actual/
+/test/integ/**/actual/
 /scripts/dependency_bundle/
 /wheels/
 **/otls/backup

.gitignore

@@ -50,7 +50,7 @@ hatch run test -k "test_name"                     # One test by name
 hatch run all:test                                # All supported Python versions
 ```
 
-**Integration Tests (Windows Only):** See [`test/AGENTS.md`](test/AGENTS.md).
+**Integration Tests:** See [`test/AGENTS.md`](test/AGENTS.md).
 
 ## Linting
 

AGENTS.md

@@ -32,11 +32,13 @@ To develop the Python code in this repository you will need:
    of Python on the same system. When running unit tests against all supported Python versions, for instance.
 2. The [hatch](https://github.com/pypa/hatch) package installed (`pip install --upgrade hatch`) into your Python environment.
 3. An install of a supported version of Cinema 4D.
-4. A valid AWS Account.
-5. An AWS Deadline Cloud Farm to run jobs on. We recommend following the quickstart in the Deadline Cloud console to create a
-   Queue with the default Queue Environment, and a Service Managed Fleet.
 
-You can develop on any Windows workstation. 
+The xa11y integration suite uses an offline mock Deadline backend, so it does
+not require an AWS account or farm. A real AWS account, farm, queue, and fleet
+are only required when testing jobs on Deadline Cloud.
+
+Submitter and xa11y development are supported on Windows and macOS. Adaptor
+development is supported on Windows and Linux.
 
 ## Software Architecture
 
@@ -51,7 +53,7 @@ from any directory of this repository:
 * `hatch build` - To build the installable Python wheel and sdist packages into the `dist/` directory.
 * `hatch run test` - To run the PyTest unit tests found in the `test/unit` directory. See [Testing](#testing).
 * `hatch run all:test` - To run the PyTest unit tests against all available supported versions of Python.
-* `hatch run integ:test` - To run all the integration tests against your current build.
+* `hatch run integ:test` - To run the xa11y integration tests against your current build.
 * `hatch run lint` - To check that the package's formatting adheres to our standards.
 * `hatch run fmt` - To automatically reformat all code to adhere to our formatting standards.
 * `hatch shell` - Enter a shell environment that will have Python set up to import your development version of this package.
@@ -90,7 +92,7 @@ The tests for the plug-in have two forms:
 
 ##### Unit Tests
 
-Unit tests are all located under the `test/deadline_submitter_for_cinema4d/unit` directory of this repository. If you are adding
+Unit tests are located under the `test/unit/deadline_submitter_for_cinema4d/` directory of this repository. If you are adding
 or modifying functionality, then you will almost always want to be writing one or more unit tests to demonstrate that your
 logic behaves as expected and that future changes do not accidentally break your change.
 
@@ -186,7 +188,7 @@ This should have automatically added the latest patch onto the S3 bucket for the
 
 ##### Unit tests
 
-Unit tests are all located under the `test/deadline_adaptor_for_cinema4d/unit` directory of this repository. If you are adding
+Unit tests are located under the `test/unit/deadline_adaptor_for_cinema4d/` directory of this repository. If you are adding
 or modifying functionality, then you will almost always want to be writing one or more unit tests to demonstrate that your
 logic behaves as expected and that future changes do not accidentally break your change.
 
@@ -200,83 +202,34 @@ hatch run test
 
 ### Integration Tests
 
-We run integration tests by running it in Cinema 4D's python i.e. c4dpy for submitter and using Commandline.exe for adaptor tests. 
-
-#### Test Flow
-1. Scene generation:
-   - Each test case uses scene generation scripts to create test scenes (and assets if necessary)
-   - Scenes are created with specific configurations for testing different scenarios
-
-2. Job bundle generation:
-   - Generated scenes are processed through the submitter code
-   - Job bundles are exported to a temporary location within the /integ folder.
+The xa11y suite launches the real Cinema 4D submitter, drives its UI against an
+offline mock Deadline backend, validates the exported job bundle, and renders
+the bundle on Windows. Cinema 4D and renderer licensing must be configured.
 
-3. Validation of job bundle:
-   - Exported bundles are compared against expected bundles
-   - Tests verify structure and content of the exports.
-
-4. Scene rendering:
-   - The job bundles are run using OpenJD `run` command with Cinema 4D Commandline. 
+#### Test Structure
 
-5. Validation of output files:
-   - The generated output files are compared with expected scene files. 
+```text
+test/integ/
+├── test_cinema4d.py               # Orchestrates scene build, UI export, and validation
+├── conftest.py                    # Cinema 4D and mock Deadline fixtures
+├── submitter_ui.py                # xa11y controls for the submitter dialog
+├── utils.py                       # Scene, bundle, and render helpers
+├── fixtures/auto_open_submitter/  # Test-only plugin that opens the submitter
+└── test_cases/<name>/
+    ├── input/
+    │   ├── scene.py               # Builds the Cinema 4D scene
+    │   └── configure.py           # Optional xa11y dialog configuration
+    ├── expected/
+    │   ├── job_bundle/            # Golden bundle files
+    │   └── renders/               # Golden render images
+    └── actual/                    # Gitignored runtime output
+```
 
-#### Test Structure
+Run the suite with:
 
-<pre>
-   /test
-      /integ
-         /test_scenes/           
-            /scene_1
-               /expected_job_bundle/      # Reference job bundle for validation
-                  asset_references.yaml
-                  parameter_values.yaml
-                  template.yaml 
-               /expected_job_output/
-                  renders/
-                     output files
-               /scene
-                  scene.py      # Contains test scene generation scripts
-         conftest.py            # Test configuration and fixtures
-         test_cinema4d.py       # Runs all the tests scenes in a parametrized fashion.
-</pre>
-
-You would have to setup Cinema 4D and Redshift licensing before you run the tests.
-For Cinema 4D licensing, set environment variable by using `$env:g_licenseServerURL = <your-license-server-host>:<port>` on Windows Powershell. 
-For redshift licensing, set the environment variable by using `$env:redshift_LICENSE = <port>@<your-license-server-host>` on Windows Powershell. 
-Or
-You can also run `c4dpy` and `Commandline.exe` separately and set the license information there. 
-1. Set the environment variable `C4D_LOCATION` to the installation folder of Cinema 4D.
-   1. `set C4D_LOCATION=<Cinema 4D location>` on Windows Command or `$env:C4D_LOCATION = <Cinema 4D location>` on Windows Powershell.
-      1. The default location for `Cinema 4D` on Windows is `C:\Program Files\Maxon Cinema 4D 2026\`. This location would be automatically used if the directory exists.
-2. For running the adaptor tests, we would need to install `pywin32` to the installation paths as its an adaptor dependency.
-
-   > **Important: Python version must match Cinema 4D's bundled Python.**
-   >
-   > Cinema 4D 2026 bundles Python 3.11. Your system Python and hatch must also use 3.11 to avoid DLL version conflicts.
-   >
-   > Using a different version (e.g., 3.13) will cause pywin32 DLLs to be built for the wrong version, resulting in:
-   > ```
-   > ImportError: Module use of python313.dll conflicts with this version of Python.
-   > ```
-   >
-   > To ensure compatibility:
-   > 1. Install Python 3.11 and make it your default (`python --version` should show 3.11.x)
-   > 2. Install hatch using Python 3.11 (`python -m pip install hatch`)
-   > 3. Use Python 3.11's pip for the pywin32 install below
-   >
-   > You can verify Cinema 4D's Python version by checking the `resource/modules/python/libs/` folder inside your Cinema 4D installation directory.
-
-   2.1 Run `pip install pywin32==308 -t <your Python site-packages location>`
-       * e.g. `pip install pywin32==308 -t "C:\Program Files\Maxon Cinema 4D 2026\resource\modules\python\libs\win64\lib\site-packages"`
-   
-   During testing, pywin32's version 308 was required because of other dependencies requiring this version.
-   2.2. Copy PyWin32 DLLs (there are some post installation things required for PyWin32):
-    * Copy `pythoncom311.dll` and `pywintypes311.dll`.
-    * From: `C:\Program Files\Maxon Cinema 4D 2026\resource\modules\python\libs\win64\lib\site-packages\pywin32_system32`
-    * To: `C:\Program Files\Maxon Cinema 4D 2026\resource\modules\python\libs\win64\dlls`
-3. Set the environment variable `PYTHONIOENCODING` to `utf-8` so that the test can use non-ASCII characters.
-
-
-3. Run `hatch run integ:test`
+```bash
+hatch run integ:test
+```
 
+See [`test/AGENTS.md`](test/AGENTS.md) for platform support, setup, focused runs,
+test-case authoring, selector discovery, and golden-bundle capture.

DEVELOPMENT.md

@@ -32,44 +32,18 @@ deps = "pip install -r requirements-release.txt"
 bump = "semantic-release -v --strict version --no-push --no-commit --no-tag --skip-build {args}"
 version = "semantic-release -v --strict version --print {args}"
 
+# Drives the real Deadline Cloud submitter dialog end-to-end with xa11y.
 [envs.integ]
-pre-install-commands = [
-  "pip install -r requirements-testing.txt"
-]
-
-[envs.integ.scripts]
-test = "pytest --no-cov {args:test/integ} -vvv --numprocesses=1"
-
-# xa11y-driven integration test. Drives the real Deadline Cloud submitter
-# dialog end-to-end. Will replace `integ` once we're happy with it.
-[envs.integ-xa11y]
 python = "3.11"
 pre-install-commands = [
   "pip install -r requirements-testing.txt"
 ]
 
-[envs.integ-xa11y.env-vars]
+[envs.integ.env-vars]
 PYTHONIOENCODING = "utf-8"
 
-[envs.integ-xa11y.scripts]
-test = "pytest --no-cov {args:test/integ_xa11y} -vvv --numprocesses=1"
+[envs.integ.scripts]
+test = "pytest --no-cov {args:test/integ} -vvv --numprocesses=1"
 
 [envs.installer.scripts]
 build-installer = "python {root}/scripts/build_installer_cli.py --installer-source-path {root}/installer/DeadlineCloudForCinema4dSubmitter.xml {args:}"
-
-[envs.integ-ci]
-pre-install-commands = [
-  "pip install -r requirements-testing.txt"
-]
-
-[[envs.integ-ci.matrix]]
-cinema4d = ["2025", "2026"]
-python = ["3.11"]
-
-[envs.integ-ci.env-vars]
-C4D_VERSION = "{matrix:cinema4d}"
-PYTHONIOENCODING = "utf-8"
-
-[envs.integ-ci.scripts]
-setup = "python ./pipeline/setup-runner.py --versions {matrix:cinema4d} {args}"
-integ = "pytest --no-cov {args:test/integ} -vvv --numprocesses=1"