Collaborative mode — multi-operator test plan execution

[ThomasMalletCodra]

Description

Allow multiple operators to work on the same test plan simultaneously, each executing and validating different tests. This is useful for large test campaigns where a single operator cannot run all tests alone (e.g., hardware-dependent tests on different machines).

Current behavior

• Test plans are single-user: one operator runs all tests sequentially.
• No locking or synchronization mechanism.
• Sharing a test plan file risks conflicts and data loss.

Expected behavior

• A test plan can be "shared" across multiple ModuleTester instances.
• Each operator claims/locks specific tests to avoid duplication.
• Results from all operators are merged into a single campaign report.
• Real-time or near-real-time status sync (e.g., via file polling or lightweight server).
• Conflict resolution if two operators modify the same test.

Implementation ideas

1. File-based (simple): Shared network directory with lock files per test item. Each operator's ModuleTester polls for changes.
2. Server-based (robust): Central coordination server (REST API) that manages test assignments and collects results.
3. Test items get an assigned_to field and a locked_by field.
4. Merge logic: combine results from multiple operators into one campaign.
5. UI indicators: show which tests are locked/claimed by other operators.

Acceptance criteria

• Multiple ModuleTester instances can share a test plan
• Tests can be assigned/claimed by individual operators
• Results from multiple operators are merged into one campaign
• Conflicts are detected and handled gracefully
• Operator status is visible in the UI (who is working on what)