Skip to content

Document unified UI automation framework for test workflows and AI tooling #994

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
Copilot wants to merge 2 commits into
base: dev
Choose a base branch
from
+18 −0
Draft

Document unified UI automation framework for test workflows and AI tooling #994

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
40791bf
Initial plan
Copilot Jun 1, 2026
52b41a3
Document UI automation framework recommendation
Copilot Jun 1, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions Testing/Temporary/CTestCostData.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
---
17 changes: 17 additions & 0 deletions docs/agents/core.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -61,6 +61,23 @@ ResInsight includes Python integration via gRPC when `RESINSIGHT_ENABLE_GRPC=ON`
- **Testing**: Cross-platform automated testing on RHEL, Ubuntu, and Windows 11
- **Build Configuration**: Key option `RESINSIGHT_TREAT_WARNINGS_AS_ERRORS` available in CMake presets

## UI Automation and UI Testing

For UI-level testing (for example create/edit/delete range filter and verify visible cells), use a shared automation architecture that supports both CI tests and AI tooling:

- **Automation transport**: expose a localhost-only automation API from ResInsight using `Qt Http Server` (`qthttpserver`).
- **Automation client/test runner**: use `Playwright` to call the automation API and assert outcomes.

This combines both requested use cases in one solution:
- deterministic UI workflow tests in CI
- the same UI operations available to AI tooling

### Alternatives Considered

- **Qt Test only (`QTest`)**: good for in-process widget tests, but less suitable as a reusable interface for external AI tooling.
- **Squish**: strong GUI automation, but adds commercial licensing/maintenance overhead.
- **Playwright only (no in-app API)**: strong runner/assertions, but desktop Qt event targeting becomes brittle without a stable in-app automation surface.

## Common File Locations

- Main CMake configuration: `/workspace/CMakeLists.txt`
Expand Down