Use verify_mock_vuforia on TestTargetStatusNotSuccess

[adamtheturtle]

Summary

• Added processing_target_id field to VuMarkCloudDatabase fixture to support testing VuMark targets in processing state across all test backends
• Refactored _vumark_database() to include both a success-state and processing-state VuMark target in the mock setup
• Updated Docker backend fixture to iterate over all VuMark targets instead of unpacking a single target
• Refactored TestTargetStatusNotSuccess test methods to accept vumark_vuforia_database fixture and removed internal MockVWS contexts, enabling these tests to run against real Vuforia, in-memory mock, and Docker mock backends via @pytest.mark.usefixtures("verify_mock_vuforia")
• Removed unused imports (MockVWS, VuMarkDatabase, VuMarkTarget) from test file

🤖 Generated with Claude Code

---

Note

Medium Risk
Moderate risk because it changes test fixtures and backend setup shared across multiple test backends (real, in-memory, docker), which can affect test determinism and CI behavior; no production code paths are modified.

Overview
Adds a new processing_target_id to the vumark_vuforia_database credentials fixture (auto-generated when not provided) to support consistently referencing a VuMark target intended to remain in PROCESSING.

Updates the mock/docked backend setup to provision two VuMark targets (ready + long-processing) and, for the docker-backed mock, iterates over all vumark_targets when posting them to the Target Manager API.

Refactors VuMark generation tests to rely on the shared fixtures/backends instead of ad-hoc MockVWS setup: the “successful target” test now runs under verify_mock_vuforia (all backends), while PROCESSING-state assertions are moved into a mock-only TestProcessingTarget using mock_only_vuforia, and unused mock imports are removed.

^{Written by Cursor Bugbot for commit 2b51f08. This will update automatically on new commits. Configure here.}

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.}