Skip to content

Conversation

@individual-it
Copy link
Contributor

@individual-it individual-it commented Oct 16, 2025

There have been at least multiple issues why the client config was not correctly cleaned up after the tests:

  1. the accounts on the server have been deleted before the client cleanup, causing the client to be stuck in the login window
  2. and child_widget.objectName caused the code to never go into that path, so the cleanup was never attempted
  3. get_active_widget() has also to ignore widgets where the name is empty

@anon-pradip
Copy link
Contributor

anon-pradip commented Nov 3, 2025

Looks like the access denied error is not produced again with this PR for those tests where Account toolbar appears in the last step in the AUT so that account cleanup happens properly . But in some scenarios the AUT doesn't get closed so that the clean up does not happen properly.
For example, Scenario: Check default options in advanced configuration:

Screencast.from.2025-11-03.11-55-22.mp4
Log Closing 'QFileDialog' window November 3, 2025 at 11:56:10 AM +05:45 C:\Users\vboxuser\projects\desktop\test\gui\shared\scripts\bdd_hooks.py:232

Detail Object '{container={container={name='dialogStack' type='QStackedWidget' visible='1' window={name='Settings' type='OCC::SettingsDialog' visible='1'}} name='quickWidget' type='OCC::QmlUtils::OCQuickWidget' visible='1'} type='RowLayout' visible='true'}' not found. Could not match properties:
    container for object name: '{container={container={name='dialogStack' type='QStackedWidget' visible='1' window=:settings_OCC_SettingsDialog} name='quickWidget' type='OCC::QmlUtils::OCQuickWidget' visible='1'} type='RowLayout' visible='true'}'
    type for object name: '{name='dialogStack' type='QStackedWidget' visible='1' window=:settings_OCC_SettingsDialog}'  C:\Users\vboxuser\projects\desktop\test\gui\shared\scripts\pageObjects\Toolbar.py:110
image

As we can see Toolbar is not found due to which the clean up does not happen properly. And when we run test again, we get the access denied error

@individual-it
Copy link
Contributor Author

Hmm, in those cases we need to click "cancel" and then no cleanup should be needed or "finish" and then do the normal cleanup

@individual-it
Copy link
Contributor Author

@anon-pradip please review again I found an other issue and fixed it

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Failed to register sync root after re-adding recently removed account connection in Windows OS

3 participants