sikuli-driver team mailing list archive

[Simon O'Connor <simon@xxxxxxxxxxxxxxx>]

Public bug reported:

Define a setUp and tearDown and one or more tests. Run them from the
Unit Test view. During the running of the unit tests, press stop in the
unit test floating dialogue.

The IDE returns, but the test continues, and will find the regions it's
looking for within the ide script and interact with them, causing all
sorts of weird behaviour. Letting the unit tests run themselves to
completion does not result in this behaviour.

Sikuli IDE Version: Sikuli X-1.0rc3(r905)
Windows 7 Professional 64Bit

** Affects: sikuli
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Sikuli
Drivers, which is subscribed to Sikuli.
https://bugs.launchpad.net/bugs/924581

Title:
  Stopping unit test does not actually stop execution

Status in Sikuli:
  New

Bug description:
  Define a setUp and tearDown and one or more tests. Run them from the
  Unit Test view. During the running of the unit tests, press stop in
  the unit test floating dialogue.

  The IDE returns, but the test continues, and will find the regions
  it's looking for within the ide script and interact with them, causing
  all sorts of weird behaviour. Letting the unit tests run themselves to
  completion does not result in this behaviour.

  Sikuli IDE Version: Sikuli X-1.0rc3(r905)
  Windows 7 Professional 64Bit

To manage notifications about this bug go to:
https://bugs.launchpad.net/sikuli/+bug/924581/+subscriptions