Hi there,
The issue you're describing—where alarmstatus_wpf.exe crashes only when run via FinalBuilder but works fine when launched manually through TestComplete—could be related to differences in the execution environment.
Some possible root causes to consider:
- User permissions or context: FinalBuilder might be running under a different user account or as a service, which could restrict UI access or permissions required by your WPF app.
- Non-interactive desktop session: WPF apps often require an interactive session. If FinalBuilder is running in a headless or non-interactive session (e.g., as part of CI/CD), this could cause the app to crash.
- Missing environment variables or dependencies: The environment under which FinalBuilder runs might be missing things available in your manual session—like specific PATH values or user-level configuration files.
- Different test configs or parameters: Double-check if FinalBuilder is triggering the same test configuration or scripts as your manual run.
Suggestions:
- Try running FinalBuilder manually in the same session as your manual TestComplete test to isolate whether it’s a session/context issue.
- Compare environment variables and user permissions between both execution paths.
- Make sure TestComplete (or TestExecute) is being run in an interactive user session when triggered by FinalBuilder.
🤖 AI-assisted response
💬 Found the answer helpful? Give it a Kudos by clicking Like!
✅ Got your issue resolved? Click Mark as Solution so others can find it quickly.
