sikuli-driver team mailing list archive

[J <1178428@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

Sikuli version: r930
Operating system: Mac 10.7.5, 64 bit

Hello!

For some time I have been having troubles with getting a Sikuli test to
run in my Eclipse project on my Mac until today. In the project I have a
folder named "libs" in which all the necessary .jar files are stored to
be used by the automated tests. It works fine to have this "libs" folder
while on a Windows machine, however no Sikuli tests will run when it is
on a Mac. I found that if I changed the name to something else, e.g.
"libraries", it will work perfectly. My guess is that Sikuli is getting
confused and trying to access the wrong "libs" folder, accessing the one
in the Eclipse project instead of a different one.

Here are some step by step instructions:

1.  Set up Eclipse to use 32 bit Java 6 and have the SikuliScript variable pointing to /Applications/Sikuli-IDE.app/Contents/Resources/Java/sikuli-script.jar in the build path (standard Sikuli installation)
2.  Open Eclipse and create any project, for example "TestProject"
3.  Create a package for your test "com.test.bug"
4.  Create a class called "BugTest"
5.  Copy and paste the following code into BugTest:

package com.test.bug;

import org.junit.Test;
import org.sikuli.script.App;

public class BugTest
{
     @Test
     public void testBugTest()
     {
          App.open("Safari");
     }
}

5.  In the project, create a folder called "libs"
6.  Import any .jar file into this folder
7.  Try to run BugTest as a JUnit 4 test and notice it will fail
8.  Rename the "libs" folder created in step 5 to be "libraries"
9.  Run BugTest
10.  Notice that the test now runs as expected

I was very surprised that this was the problem because using "libs" as a
folder name seems to be pretty standard. Please let me know if you need
any more information, I'd be happy to help.

** Affects: sikuli
     Importance: Undecided
         Status: New

** Description changed:

  Sikuli version: r930
  Operating system: Mac 10.7.5, 64 bit
  
  Hello!
  
  For some time I have been having troubles with getting a Sikuli test to
  run in my Eclipse project on my Mac until today. In the project I have a
  folder named "libs" in which all the necessary .jar files are stored to
  be used by the automated tests. It works fine to have this "libs" folder
  while on a Windows machine, however no Sikuli tests will run when it is
  on a Mac. I found that if I changed the name to something else, e.g.
  "libraries", it will work perfectly. My guess is that Sikuli is getting
  confused and trying to access the wrong "libs" folder, accessing the one
  in the Eclipse project instead of a different one.
  
  Here are some step by step instructions:
  
  1.  Set up Eclipse to use 32 bit Java 6 and have the SikuliScript variable pointing to /Applications/Sikuli-IDE.app/Contents/Resources/Java/sikuli-script.jar in the build path (standard Sikuli installation)
  2.  Open Eclipse and create any project, for example "TestProject"
  3.  Create a package for your test "com.test.bug"
  4.  Create a class called "BugTest"
  5.  Copy and paste the following code into BugTest:
  
- package com.testcases.poc;
-  
+ package com.test.bug;
+ 
  import org.junit.Test;
  import org.sikuli.script.App;
-  
+ 
  public class BugTest
  {
-      @Test
-      public void testBugTest()
-      {
-           App.open("Safari");
-      }
+      @Test
+      public void testBugTest()
+      {
+           App.open("Safari");
+      }
  }
  
  5.  In the project, create a folder called "libs"
  6.  Import any .jar file into this folder
  7.  Try to run BugTest as a JUnit 4 test and notice it will fail
  8.  Rename the "libs" folder created in step 5 to be "libraries"
  9.  Run BugTest
  10.  Notice that the test now runs as expected
  
  Please let me know if you need any more information, I'd be happy to
  help.

** Description changed:

  Sikuli version: r930
  Operating system: Mac 10.7.5, 64 bit
  
  Hello!
  
  For some time I have been having troubles with getting a Sikuli test to
  run in my Eclipse project on my Mac until today. In the project I have a
  folder named "libs" in which all the necessary .jar files are stored to
  be used by the automated tests. It works fine to have this "libs" folder
  while on a Windows machine, however no Sikuli tests will run when it is
  on a Mac. I found that if I changed the name to something else, e.g.
  "libraries", it will work perfectly. My guess is that Sikuli is getting
  confused and trying to access the wrong "libs" folder, accessing the one
  in the Eclipse project instead of a different one.
  
  Here are some step by step instructions:
  
  1.  Set up Eclipse to use 32 bit Java 6 and have the SikuliScript variable pointing to /Applications/Sikuli-IDE.app/Contents/Resources/Java/sikuli-script.jar in the build path (standard Sikuli installation)
  2.  Open Eclipse and create any project, for example "TestProject"
  3.  Create a package for your test "com.test.bug"
  4.  Create a class called "BugTest"
  5.  Copy and paste the following code into BugTest:
  
  package com.test.bug;
  
  import org.junit.Test;
  import org.sikuli.script.App;
  
  public class BugTest
  {
       @Test
       public void testBugTest()
       {
            App.open("Safari");
       }
  }
  
  5.  In the project, create a folder called "libs"
  6.  Import any .jar file into this folder
  7.  Try to run BugTest as a JUnit 4 test and notice it will fail
  8.  Rename the "libs" folder created in step 5 to be "libraries"
  9.  Run BugTest
  10.  Notice that the test now runs as expected
  
- Please let me know if you need any more information, I'd be happy to
- help.
+ I was very surprised that this was the problem because using "libs" as a
+ folder name seems to be pretty standard. Please let me know if you need
+ any more information, I'd be happy to help.

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

Title:
  Can't use a folder named "libs" in Eclipse project

Status in Sikuli:
  New

Bug description:
  Sikuli version: r930
  Operating system: Mac 10.7.5, 64 bit

  Hello!

  For some time I have been having troubles with getting a Sikuli test
  to run in my Eclipse project on my Mac until today. In the project I
  have a folder named "libs" in which all the necessary .jar files are
  stored to be used by the automated tests. It works fine to have this
  "libs" folder while on a Windows machine, however no Sikuli tests will
  run when it is on a Mac. I found that if I changed the name to
  something else, e.g. "libraries", it will work perfectly. My guess is
  that Sikuli is getting confused and trying to access the wrong "libs"
  folder, accessing the one in the Eclipse project instead of a
  different one.

  Here are some step by step instructions:

  1.  Set up Eclipse to use 32 bit Java 6 and have the SikuliScript variable pointing to /Applications/Sikuli-IDE.app/Contents/Resources/Java/sikuli-script.jar in the build path (standard Sikuli installation)
  2.  Open Eclipse and create any project, for example "TestProject"
  3.  Create a package for your test "com.test.bug"
  4.  Create a class called "BugTest"
  5.  Copy and paste the following code into BugTest:

  package com.test.bug;

  import org.junit.Test;
  import org.sikuli.script.App;

  public class BugTest
  {
       @Test
       public void testBugTest()
       {
            App.open("Safari");
       }
  }

  5.  In the project, create a folder called "libs"
  6.  Import any .jar file into this folder
  7.  Try to run BugTest as a JUnit 4 test and notice it will fail
  8.  Rename the "libs" folder created in step 5 to be "libraries"
  9.  Run BugTest
  10.  Notice that the test now runs as expected

  I was very surprised that this was the problem because using "libs" as
  a folder name seems to be pretty standard. Please let me know if you
  need any more information, I'd be happy to help.

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