IDE-314: Stabilize and optimize sensor list tests with Robolectric integration test

[harshsomankar123-tech]

Description

Jira Ticket: IDE-314 (https://catrobat.atlassian.net/browse/IDE-314)

This PR overhauls the FormulaEditorSensorList testing strategy. We replaced the slow, flakey Espresso verification with a comprehensive Robolectric integration test that successfully validates the content and ordering of all 160+ sensor items across 16 different categories.

Key Changes

• New Integration Test: Added FormulaEditorSensorListIntegrationTest.kt (Robolectric).
  • Verifies the entire sensor list (headers, item names, and ordering) in under 3 seconds.
  • Implemented reflection-based mocking for SensorHandler to simulate 100% hardware availability (Accelerometer, Compass, etc.) in a headless environment.
  • Handled Koin-injected dependencies to resolve previous NullPointerException issues.
• Espresso Optimization: Refactored FormulaEditorSensorListTest.kt.
  • Slimmed down from hundreds of data-heavy assertions to 8 high-value interaction tests.
  • Focuses on UI behavior (opening/closing the list, search filtering) rather than exhaustive raw data checks.
• Architecture Stabilization:
  • Synchronized ProjectManager and SensorHandler singletons between the test runner and the application context.
  • Simplified test setup using AppCompatActivity as a lightweight context provider.

Verification Plan

• Robolectric Integration: Ran ./gradlew testCatroidDebugUnitTest --tests "*FormulaEditorSensorListIntegrationTest*" (Passed).
• Espresso Smoke Tests: Ran ./gradlew connectedCatroidDebugAndroidTest --tests "*FormulaEditorSensorListTest*" (Passed).
• Edge Cases: Verified that AI-specific sensors (Pose Detection, Object Recognition) and connectivity-based sensors (Drone, Cast) are correctly populated when their respective settings are enabled.

Performance Impact

Metric	Before (Espresso Only)	After (Hybrid Strategy)
Runtime	~5-8 mins (flaky)	~3s (Robolectric) + ~30s (Espresso)
Coverage	Partial verification	100% data parity verification

Your checklist for this pull request

Please review the contributing guidelines and wiki pages of this repository.

• Include the name of the Jira ticket in the PR’s title
• Include a summary of the changes plus the relevant context
• Choose the proper base branch (develop)
• Confirm that the changes follow the project’s coding guidelines
• Verify that the changes generate no compiler or linter warnings
• Perform a self-review of the changes
• Verify to commit no other files than the intentionally changed ones
• Include reasonable and readable tests verifying the added or changed behavior
• Confirm that new and existing unit tests pass locally
• Check that the commits’ message style matches the project’s guideline
• Stick to the project’s gitflow workflow
• Verify that your changes do not have any conflicts with the base branch
• After the PR, verify that all CI checks have passed
• Post a message in the catroid-stage or catroid-ide Slack channel and ask for a code reviewer

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud