Open pputre opened 2 years ago
Yep. Happy to. I think this is the case when there is an invisible overlay on the screen which we put up to prevent the user from interacting with the screen when the app is not stable. The user will just retry the action. I'll add the option when I get back next week. I'm in the Cape this week.
On Wed, Aug 10, 2022, 12:57 PM pputre @.***> wrote:
There are times when a recorded mouse click does not seem execute and the screen comparison fails. I manually re-execute the click and then the test goes on it's merry way. Can we add an option for a mouse click retry attempt if the expected screen is significantly different after a failure (maybe use a set/configurable pixel minimum). This appears mostly when I try to loop the STT's to run through x (3) times.
— Reply to this email directly, view it on GitHub https://github.com/zacfilan/brimstone-recorder/issues/242, or unsubscribe https://github.com/notifications/unsubscribe-auth/AVIGSUEVUJPG2R7SWSC5663VYPNRHANCNFSM56FHX6JQ . You are receiving this because you are subscribed to this thread.Message ID: @.***>
There are times when a recorded mouse click does not seem execute and the screen comparison fails. I manually re-execute the click and then the test goes on it's merry way. Can we add an option for a mouse click retry attempt if the expected screen is significantly different after a failure (maybe use a set/configurable pixel minimum). This appears mostly when I try to loop the STT's to run through x (3) times.