Workaround for PopupWatcher causin LineageGlueRule exception
Posted: Fri Jul 07, 2017 1:14 pm
Hi,
Me and my colleague stumbled into an exception that was occuring when a PopupWatcher was being started up.
We got the LineageGlueRule exception variant that say Key not found.
After some intense debugging, we finally found out how to avoid it, so I'm sharing it here
Insert a delay after the code that starts up the PopupWatcher. It appears that the PopupWatcher needs some stability in the GUI while it is starting up, and any action that modifies or changes the SUT GUI risks disrupting whatever the PopupWatcher is doing while starting up.
May this save you from hours of debugging.
Me and my colleague stumbled into an exception that was occuring when a PopupWatcher was being started up.
We got the LineageGlueRule exception variant that say Key not found.
After some intense debugging, we finally found out how to avoid it, so I'm sharing it here
Insert a delay after the code that starts up the PopupWatcher. It appears that the PopupWatcher needs some stability in the GUI while it is starting up, and any action that modifies or changes the SUT GUI risks disrupting whatever the PopupWatcher is doing while starting up.
May this save you from hours of debugging.