sikuli-driver team mailing list archive
-
sikuli-driver team
-
Mailing list archive
-
Message #24645
[Bug 1289299] [NEW] [request] want the option to specify a FindFailed handler, that is called on FindFailed
Public bug reported:
Hi,
This is more of a feature request (unless a way exists to closely mimick
this).
It would be nice to be able to specify a user defined handler as the
action in case Sikuli fails to find an image. When we setup a set of
tests to run on a periodic basis, I would imagine that many users would
want to capture a screenshot of the application window on a failure. If
we could specify a screen grabbing function as the action to be taken on
a failure, that would save some typing with each test to invoke it
explicitly as part of the exception handling code.
Thanks.
** Affects: sikuli
Importance: Medium
Assignee: RaiMan (raimund-hocke)
Status: Fix Committed
** Changed in: sikuli
Status: New => Fix Committed
** Changed in: sikuli
Importance: Undecided => Medium
** Changed in: sikuli
Assignee: (unassigned) => RaiMan (raimund-hocke)
** Changed in: sikuli
Milestone: None => 1.2.0
--
You received this bug notification because you are a member of Sikuli
Drivers, which is subscribed to Sikuli.
https://bugs.launchpad.net/bugs/1289299
Title:
[request] want the option to specify a FindFailed handler, that is
called on FindFailed
Status in Sikuli:
Fix Committed
Bug description:
Hi,
This is more of a feature request (unless a way exists to closely
mimick this).
It would be nice to be able to specify a user defined handler as the
action in case Sikuli fails to find an image. When we setup a set of
tests to run on a periodic basis, I would imagine that many users
would want to capture a screenshot of the application window on a
failure. If we could specify a screen grabbing function as the action
to be taken on a failure, that would save some typing with each test
to invoke it explicitly as part of the exception handling code.
Thanks.
To manage notifications about this bug go to:
https://bugs.launchpad.net/sikuli/+bug/1289299/+subscriptions
Follow ups
References