| 2011-08-15 14:10:51 |
j |
bug |
|
|
added bug |
| 2011-08-15 16:42:33 |
RaiMan |
summary |
X1.0rc2 Unittests not working with some scriptnames when called via commandline |
X-1.0rc2 Unittests not working with some scriptnames when called via commandline |
|
| 2011-08-15 16:42:47 |
RaiMan |
summary |
X-1.0rc2 Unittests not working with some scriptnames when called via commandline |
X-1.0rc2 Unittests not working with some scriptnames when called via command line with -t |
|
| 2011-08-15 16:48:27 |
RaiMan |
summary |
X-1.0rc2 Unittests not working with some scriptnames when called via command line with -t |
X-1.0rc2 Unittests not working with some scriptnames when called via command line with -t --- possible workaround |
|
| 2011-08-15 16:49:16 |
RaiMan |
description |
This Bug was reproducable with the combinations WinXP & rc2 as well as with Win7 & rc3.
When executing a Sikuli-test via commandline like
sikuli-ide.bat -t <test.sikuli>
sikuli has some odd behavior: The script does in some cases not load at all but only prints [error] null, and in other cases refuses to find any kind of image on the screen, resolving in FindFailed-Exceptions.
A quick test revealed the following correlation between name of the sikuli-script and the mentioned behavior:
All scripts where executed as
Filenames a.sikuli as well as b.sikuli resolved in a Find Failed Exception for every find() in the script.
Filenames c.sikuli, d.sikuli, e.sikuli and m.sikuli worked normal.
Filenames f.sikuli and x.sikuli did nothing but printing [error] null
I did not test more filenames yet.
Look here for all the detail https://answers.launchpad.net/sikuli/+question/167514 (last posts) |
--- possible workaround
script names starting with the letters c or m seem to work.
-----------------------------------------------------------
This Bug was reproducable with the combinations WinXP & rc2 as well as with Win7 & rc3.
When executing a Sikuli-test via commandline like
sikuli-ide.bat -t <test.sikuli>
sikuli has some odd behavior: The script does in some cases not load at all but only prints [error] null, and in other cases refuses to find any kind of image on the screen, resolving in FindFailed-Exceptions.
A quick test revealed the following correlation between name of the sikuli-script and the mentioned behavior:
All scripts where executed as
Filenames a.sikuli as well as b.sikuli resolved in a Find Failed Exception for every find() in the script.
Filenames c.sikuli, d.sikuli, e.sikuli and m.sikuli worked normal.
Filenames f.sikuli and x.sikuli did nothing but printing [error] null
I did not test more filenames yet.
Look here for all the detail https://answers.launchpad.net/sikuli/+question/167514 (last posts) |
|
| 2011-08-16 09:43:08 |
RaiMan |
summary |
X-1.0rc2 Unittests not working with some scriptnames when called via command line with -t --- possible workaround |
X-1.0rc2: Windows: Unittests not working with some scriptnames when called via command line with -t --- possible workaround |
|
| 2011-08-16 09:49:38 |
RaiMan |
description |
--- possible workaround
script names starting with the letters c or m seem to work.
-----------------------------------------------------------
This Bug was reproducable with the combinations WinXP & rc2 as well as with Win7 & rc3.
When executing a Sikuli-test via commandline like
sikuli-ide.bat -t <test.sikuli>
sikuli has some odd behavior: The script does in some cases not load at all but only prints [error] null, and in other cases refuses to find any kind of image on the screen, resolving in FindFailed-Exceptions.
A quick test revealed the following correlation between name of the sikuli-script and the mentioned behavior:
All scripts where executed as
Filenames a.sikuli as well as b.sikuli resolved in a Find Failed Exception for every find() in the script.
Filenames c.sikuli, d.sikuli, e.sikuli and m.sikuli worked normal.
Filenames f.sikuli and x.sikuli did nothing but printing [error] null
I did not test more filenames yet.
Look here for all the detail https://answers.launchpad.net/sikuli/+question/167514 (last posts) |
--- possible workaround
script names starting with the letters c or m seem to work.
-----------------------------------------------------------
*** comment on Mac:
This does not happen on Mac Lion using rc3 containing Jython 2.5.2
Did not test on Linux.
So it might be a problem of the Jython unit test feature on Windows.
I did not find any code in the Sikuli source, that depends on the filename, with the only exception, that the internally generated test class is named using the name of the Sikuli script folder.
--------------------------------------------------------------------------
This Bug was reproducable with the combinations WinXP & rc2 as well as with Win7 & rc3.
When executing a Sikuli-test via commandline like
sikuli-ide.bat -t <test.sikuli>
sikuli has some odd behavior: The script does in some cases not load at all but only prints [error] null, and in other cases refuses to find any kind of image on the screen, resolving in FindFailed-Exceptions.
A quick test revealed the following correlation between name of the sikuli-script and the mentioned behavior:
All scripts where executed as
Filenames a.sikuli as well as b.sikuli resolved in a Find Failed Exception for every find() in the script.
Filenames c.sikuli, d.sikuli, e.sikuli and m.sikuli worked normal.
Filenames f.sikuli and x.sikuli did nothing but printing [error] null
I did not test more filenames yet.
Look here for all the detail https://answers.launchpad.net/sikuli/+question/167514 (last posts) |
|
| 2012-01-17 14:57:23 |
RaiMan |
description |
--- possible workaround
script names starting with the letters c or m seem to work.
-----------------------------------------------------------
*** comment on Mac:
This does not happen on Mac Lion using rc3 containing Jython 2.5.2
Did not test on Linux.
So it might be a problem of the Jython unit test feature on Windows.
I did not find any code in the Sikuli source, that depends on the filename, with the only exception, that the internally generated test class is named using the name of the Sikuli script folder.
--------------------------------------------------------------------------
This Bug was reproducable with the combinations WinXP & rc2 as well as with Win7 & rc3.
When executing a Sikuli-test via commandline like
sikuli-ide.bat -t <test.sikuli>
sikuli has some odd behavior: The script does in some cases not load at all but only prints [error] null, and in other cases refuses to find any kind of image on the screen, resolving in FindFailed-Exceptions.
A quick test revealed the following correlation between name of the sikuli-script and the mentioned behavior:
All scripts where executed as
Filenames a.sikuli as well as b.sikuli resolved in a Find Failed Exception for every find() in the script.
Filenames c.sikuli, d.sikuli, e.sikuli and m.sikuli worked normal.
Filenames f.sikuli and x.sikuli did nothing but printing [error] null
I did not test more filenames yet.
Look here for all the detail https://answers.launchpad.net/sikuli/+question/167514 (last posts) |
--- possible workaround
script names starting with the letters c or m seem to work.
-----------------------------------------------------------
*** comment on Mac:
This does not happen on Mac Lion using rc3 containing Jython 2.5.2
Did not test on Linux.
So it might be a problem of the internal usage of JUnit on Windows.
I did not find any code in the Sikuli source, that depends on the filename, with the only exception, that the internally generated test class is named using the name of the Sikuli script folder.
--------------------------------------------------------------------------
This Bug was reproducable with the combinations WinXP & rc2 as well as with Win7 & rc3.
When executing a Sikuli-test via commandline like
sikuli-ide.bat -t <test.sikuli>
sikuli has some odd behavior: The script does in some cases not load at all but only prints [error] null, and in other cases refuses to find any kind of image on the screen, resolving in FindFailed-Exceptions.
A quick test revealed the following correlation between name of the sikuli-script and the mentioned behavior:
All scripts where executed as
Filenames a.sikuli as well as b.sikuli resolved in a Find Failed Exception for every find() in the script.
Filenames c.sikuli, d.sikuli, e.sikuli and m.sikuli worked normal.
Filenames f.sikuli and x.sikuli did nothing but printing [error] null
I did not test more filenames yet.
Look here for all the detail https://answers.launchpad.net/sikuli/+question/167514 (last posts) |
|
| 2012-11-02 14:31:34 |
RaiMan |
sikuli: status |
New |
Won't Fix |
|
| 2012-11-02 14:31:38 |
RaiMan |
sikuli: milestone |
|
x1.0 |
|
| 2012-11-02 14:31:45 |
RaiMan |
sikuli: assignee |
|
RaiMan (raimund-hocke) |
|
| 2012-11-02 17:01:26 |
RaiMan |
tags |
|
unittest |
|
| 2012-11-02 17:06:26 |
RaiMan |
sikuli: status |
Won't Fix |
In Progress |
|
| 2013-02-21 11:20:18 |
RaiMan |
sikuli: status |
In Progress |
Won't Fix |
|
| 2013-02-21 11:20:21 |
RaiMan |
sikuli: milestone |
x1.0 |
|
|
