sikuli-driver team mailing list archive

[RaiMan <rmhdevelop@xxxxxx>]

This is a known problem and should only happen, if the test run produces
an exception (other than assert), that is not handled in the script.
Using the abort key should recover from the situation.

The most common problems are syntax errors. Most of them could be
avoided, if using a normal run (this does nothing, since there are only
def()'s, but the syntax is checked).

The IDE test feature has many oddities and is on the agenda to be
rewritten. If you want to know, what is really happening, use Python's
unitttest in the normal Sikuli scripting environment.

** Summary changed:

- Run button disabled after failed unit test
+ X-1.0rc2: IDE: Run button disabled after unit test stops with an exception

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

Title:
  X-1.0rc2: IDE: Run button disabled after unit test stops with an
  exception

Status in Sikuli:
  New

Bug description:
  32 bit Windows xp SP3 
  Sikuli version: Sikuli X-1.Orc2

  When running a unit test which failes the "Run" button in the unit
  test menu is disabled. The "Run" Button is replaced with "Stop" and it
  is impossible to restart the test when some corrections is made.

  Tried to switch to another test but with the same result (Yep, the
  other test where saved).

  Summary: "Run" button in unit test menu is disabled after performing a
  non successful unit test.

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